/build/static/layout/Breadcrumb_cap_w.png

Systems Deployment Question


K2000 scripted installation fails

12/05/2014 2391 views
After having problems that are described here http://www.itninja.com/question/ntfs-problems-with-scripted-installation-after-upgrading-to-3-6 I did what I was instructed and recreated the KBE. After that Im getting "Windows installation cannot continue because a required driver could not be installed" error after Windows installation goes to "Installing updates". I have tried what is told in http://www.itninja.com/question/windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed and deleted drivers from \\k2000\drivers\ from kbe and win7 and starting from scratch. That page mentions that the error is because of "overharvesting", but the error comes with zero drivers in those folders. Also adding relevant drivers from HP website doesnt help.

If I press shift+F10 I can see that diskpart finds the disk and network is also working. What im uncertain of, that is the problem within windows_7_x64 or kbe_windows_x64 -folder? Ive tried to install the computer for at least 20 times with different drivers and KBE 3, 4 and 5 and still getting the same error and im running out of ideas.

The computer in question is HP Z420 with SSD.
2 Comments   [ + ] Show comments

Comments

  • Have you had a look in the application event log to see whether there is any specific reference to the missing driver type?
  • It doesnt boot up to windows. The error comes at the end of OS installation, when it is supposed to start driver installation. Is it possible to somehow open event log at that point somehow?

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ