/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


k2000 Driver Feed Could not find SOFTWARE Registry Key

09/17/2020 152 views

Created a Windows 10 2004 KBE x64 using Windows 10 2004 AIK and PE addon using Version 7.2.10.9 of K2000 SDA Media Manager. Our K2000 is updated to version 7.2.97.

This new KBE for Windows 10 2004 does not work properly. We have older KBE, based on 1803 and 1903, that work properly. The error comes when booting to the newly created boot environment:


Running Driver Feed Advisor

=========================

Driver Feed Advisor Version 7.0.0.0

==============================

Could not find SOFTWARE registry key on device to read Operating System

Use windows version switch to see results with desired Operating System

For example: driverfeed_advisor.exe /kbe /w10

Could not find SOFTWARE registry key on device to read Operating System  

Use windows version switch to see results with desired Operating System

For example: driverfeed_advisor.exe /kbe /w10

Running PE Version: >10<

Manufacturer reported by WMI: >Dell Inc.<

Manufacturer expected expected by driverfeed >dell<

Model reported by WMI: >Optiplex 790<

Model expected by driverfeed: >790<

OS: >OSNotFoundonLocalDrive<

Path expected by driverfeed: >dell\OSNotFoundonLocalDrive\790<

The driver path does not currently exist on the SDA


Yes you read that right. I'm trying to image Optiplex 790s from 8+ years ago.

What can I do to resolve this issue so the driver feed found by the 1803 and 1903 KBE are found by the 2004 KBE?


Thanks

Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

2

"Path expected by driverfeed: >dell\OSNotFoundonLocalDrive\790<"
It's not an error\issue, the KBE is telling you that no O.S. was detected in this device.

I suggest you try to deploy your Image as usual, and see if  at the end, you encounter any issues related to drivers missing or something.

Answered 09/18/2020 by: Channeler
Red Belt

  • Thank you for the answer. Why would this occur with only with a KBE created from windows 2004 AIK? The very same machine does not behave this way when using a KBE made with 1903 or 1803 AIK.
    I'll try pushing a known good image with the 2004 KBE and post back
    • it should happen with any KBEs.

      I have a bunch of 1903 ADK KBEs(AIKs are no more), and I tend to image VMs a LOT, since those VMs have Blank Hard Drives, I'm used to see the O.S. not found often.

      If a healthy O.S. is installed there, that line Should display the O.S.
  • You are correct that it does deploy an image. I've been able to deploy to and from the 2004 KBE.
    If an OS is installed, it does not complain.

    This seems to me to be different behavior that the 1903 and 1803 KBE, as when I boot those I get no complaints.

    Thanks for the answers
 
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