search

tabs-not-spaces / Intune.USB.Creator

A module containing tools to assist with the creation of a bootable WinPE USB used to provision devices for enrollment to Intune.
GNU General Public License v3.0
131 stars 43 forks source link

Failure after Install.wim found on drive #29

Closed hotzenwalder closed 3 years ago

hotzenwalder commented 3 years ago

Been trying to use the Intune USB Creator but every attempt on diferent systems and hardware fails after the message 'Install.wim found on drive E:\' with a WARING: FAILED message

Using latest veersion image

Here's the command used to built the USB on a 20Gb VHDX

Publish-ImageToUSB -winPEPath "https://githublfs.blob.core.windows.net/storage/WinPE.zip" -windowsIsoPath "M:\OSDBuilder\OSBuilds\Multilang NLUS 2009 NetFX3 19042.746\ISO\Win10 x64 2009 19042.746.iso" -getAutopilot Cfg

image

Here's the recursive directory information for the image partition

image

Here's the error

image

I've tried different options...

HP EliteBook 820 G6 with a USB stick build with USB creator - Fail Hyper-V virtual machine with two disk attached as per your example - Fail (running on Windows Server 2016) Hyper-V virtual machine with two disk attached as per your example - Fail (running on Windows Server 2019)

Everything needed is on the two partitions and to rule out an error in my custom install.wim I also tried with the install.wim from the ISO's available from the Microsoft Visual Studio Download site. Used 1909 and 20H2 in UK English and both failed as well

Sort of a debug attempt

image

and the last part

image

content of imageIndex.json

{ "PSComputerName": "localhost", "RunspaceId": "cbbe17e9-506e-4205-bc0f-e657f3b36412", "PSShowComputerName": false, "ImagePath": "C:\Users\MARCEL~1\AppData\Local\Temp\Win10\Images\install.wim", "ImageName": "Windows 10 Enterprise", "ImageIndex": 1, "ImageDescription": "Windows 10 Enterprise", "ImageSize": 17346414256, "LogPath": "C:\Windows\Logs\DISM\dism.log", "ScratchDirectory": null, "LogLevel": "WarningsInfo" }

Intune.USB.Creator was used on Windows Server 2016 and Windows Server 2019 both with the same results.

tabs-not-spaces commented 3 years ago

Thanks for the detailed issue - managed to repro it and found the problem was with a failed upload of the WinPE media to Azure. I've reuploaded and tested and can verify the issue is not reproducible now.

Please make sure that you delete the "Win10" folder in your temp directory and try running the cmdlet again - the WinPE media should be ~415MB.

Closing off the issue now, but reopen if your experience isn't the same as mine.

hotzenwalder commented 3 years ago

It's working with a VHDX which is great. I'm getting an error when writing to USB, but I must test with other hardware if this also throws the error below

image

Never had any issues with USB before and also don't needed to wipe the disk beforehand. If the issue remains I wil open a new issue