Another DISM/WinPE issue...

RobertKaucher

So I have managed to get the 64 bit version of WindpwsPE to work with Hyper-V but I am having issues witht he x86 ISO.

I am getting the following error when I boot to the ISO:

---

File: \windows\system32\DRIVERS\storvsc.sys

Status: 0xc000035a

Info: Windows failed to load because a critical system driver is missing, or corrupt.

---

I installed the integration components the same way I did with the 64 bit version. Using DISM to query the drivers I get the following:


Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Obtaining list of 3rd party drivers from the driver store...
Driver packages listing:
Published Name : oem0.inf
Original File Name : wnetvsc.inf
Inbox : No
Class Name : Net
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem1.inf
Original File Name : ws3cap.inf
Inbox : No
Class Name : System
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem2.inf
Original File Name : wstorvsc.inf
Inbox : No
Class Name : SCSIAdapter
Provider Name : Microsoft.
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem3.inf
Original File Name : wstorflt.inf
Inbox : No
Class Name : System
Provider Name : Microsoft Corporation
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem4.inf
Original File Name : wvmbus.inf
Inbox : No
Class Name : SYSTEM
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem5.inf
Original File Name : wvmbushid.inf
Inbox : No
Class Name : HIDClass
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem6.inf
Original File Name : wvmic.inf
Inbox : No
Class Name : System Devices
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem7.inf
Original File Name : ws3cap.inf
Inbox : No
Class Name : System
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
Published Name : oem8.inf
Original File Name : wvmbushid.inf
Inbox : No
Class Name : HIDClass
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.0.6002.18005
The operation completed successfully.

---

Any suggestions?

Hyper-Me

Why are you loading SCSI drivers for hyper-V? You can put an OS on a SCSI drive in hyper-v anyway.

WinPE should see the IDE drives without issue in hyper-v, but i dont know about the network cards.

RobertKaucher

wstorflt.inf is just one of the drivers included int he integration tools.

Hyper-Me

But why do you need the integration tools if you are just booting a VM to a volatile OS thats gone when you restart? Are you trying to actually load images and WinPE isnt seeing the IDE bus?