Driver Feed for 9020 AIO creates directory different from what driver_feed_discovery_tool shows
This is the error I am getting when booting to my KBE:
Driver Feed for 9020 AIO creates directory different from what driver_feed_discovery_tool shows. Running the driver_feed_discovery_tool.vbs on the Dell 9020 AIO shows:
My driver feed that the k2000 created looks like this:
I have tried to rename the 9020 aio folder to AIO, recached but it didnt make any difference.
For which I have tried the article here: http://www.kace.com/support/resources/kb/article/windows-setup-cannot-install-critical-boot-drivers but it did not make any difference!
Driver Feed for 9020 AIO creates directory different from what driver_feed_discovery_tool shows. Running the driver_feed_discovery_tool.vbs on the Dell 9020 AIO shows:
My driver feed that the k2000 created looks like this:
I have tried to rename the 9020 aio folder to AIO, recached but it didnt make any difference.
For which I have tried the article here: http://www.kace.com/support/resources/kb/article/windows-setup-cannot-install-critical-boot-drivers but it did not make any difference!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
SDNBTP
9 years ago
Does your base Windows 7 image contain KMDF 1.11? I had trouble imaging some newer Dells until I added this package.
http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it.aspx
Posted by:
jegolf
9 years ago
You will want to rename the share path to match the path from the script output...so after drivers_postinstall you will want dell\windows_7_x64\AIO...
Comments:
-
@jegolf Thanks for the reply. I mentioned above that I renamed the 9020 aio folder to AIO but it did not make any difference. - jason.williams 9 years ago
-
Actually I'm sorry I misread your post. For KBE drivers those are located in the \\yourkbox\drivers share. Have you tried using the latest KBE driver pack?
https://support.software.dell.com/k2000-systems-deployment-appliance/kb/111717 - jegolf 9 years ago-
Yes. I extracted the BE_driver_pack_3.zip into \\k2000\drivers\kbe_windows_x64 prior to all of this. The very first screenshot is where I am at right now with this. - jason.williams 9 years ago
-
When copying the KBE driver pack did you first copy (if you wish) and then delete all existing drivers from the directory? After recaching you also need to rebuild a new KBE via the media manager...and then make sure you boot with that new KBE as it won't be your default until you update that under Settings > Control Panel > General Settings. - jegolf 9 years ago
-
You may be able to find the problem driver by looking at this log file:
X:\Windows\Panther\setupact.log
I got this tip to help me in the past from okaas on this post:
http://www.itninja.com/question/driver-issue
"...
When the WIn7 install halts (with the above-stated message), do NOT press ok (or what-ever button) to restart the computer. Rather, ALT+TAB back to the DELL KACE 2000 Deployment client, and go in to the Recover option in the main menu, and start Notepad. Now; open the file: X:\Windows\Panther\setupact.log and check what driver was attempted to load last. Simply remove this from your driver share
..." - jegolf 9 years ago-
I will try that thank you. - jason.williams 9 years ago
-
Jason, I am having the same issue now. Did you resolve it? Can you help a poor old fella? - hoodathunkut 8 years ago
