Create Windows 10 ISO image from Existing Installation  

copyitright said:

I'm stuck at 3.8~3.9.

For some unknown reason my VM doesn't shut down after doing its thang at the "Enable System Out-of-Box Experience (OOBE)" + generalize + shutdown screen/prompt (i'm trying to sysprep a Dutch non-OEM Windows 10 Pro x64).

Which virtualization software you are using? Hyper-V, VirtualBox, VMware? What happens when you click OK? Do you have Sysprep set as in screenshot:

copyitright said:

If i'm right, my previous post's title says: "Hyper-V not shutting down VM at "Enable System Out-of-Box Experience"

I did what was stated in the screen capture (the guide is easy to follow).

Nothing happens when clicking Ok, other than the sysprep window closing and leaving me at the desktop.
It doesn't hang/freeze or whatever, i can interact with everything but it doesn't shut down the VM/OS.

Now i basically am wondering if manually shutting down the VM instead has the same result as when Hyper-V's Sysprep would do it, but i don't believe so.

Have any of you experienced the same thing? Perhaps i should try a different VM?

Sorry, I missed the post title.

Just shutting down VM is not good, Sysprep needs to be run. Try this: close Sysprep prompt by clicking Cancel button, press WIN + R to open Run prompt, type following command and click OK:

%windir%\system32\sysprep\sysprep.exe /generalize /oobe

Does Sysprep run now?

copyitright said:

Yes! But apparently (and unfortunately) it shows an error which states that it wasn't able to validate my Windows installation.

A solution i found (which didn't work) mentioned that you could delete a registry key named "Upgrade", only it wasn't there (probably because my installation wasn't an upgrade).

Whereas another solution which i haven't tried yet is to delete one or more offending/conflicting packages that could be mentioned in setupact.log.

Unless you have the answer i'll check what sysprep advices me to do (consulting %WINDIR%\System32\Sysprep\Panther\setupact.log for more information) and report back my findings.

Well, setupact.log surely has a lot of information. There are a few errors but i'm not sure if i should post the whole thing (starting from the new sysprep run) or just the errors.

I can't seem to copy/paste the text from the VM. It isn't picked up by the host OS (setting or limitation? - used to VMware's drap-n-drop/clipboard transfer stuff).

edit: I also notice that my VM client's network and sound systray icons show as "not available" (i don't know when or due to what this happened).

I also read that you can only use the sysprep command 8 times for the same image? :-/


Here are the warnings/errors that showed up during the sysprep run (typed by hand):

Code:

Warning             SYSPRP WinMain: File operations pending
Error                   SYSPRP Failed to remove apps for the current user: 0x80670006.
Error                   SYSPRP Exit code of RemoveAllApps thread was 0x80670006.
Error                   SYSPRP ActionPlatform::LaunchModue: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x80670006
Error                   SYSPRP SysprepSession::Validate: Error in validating actions from  C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml;  dwRet = 0x80670006
Error                   SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x80670006
Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x80670006
Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80670006

The most frequent occurance i see is: 0x80670006

Perhaps this will help me to get around it: https://support.microsoft.com/en-us/help/2769827/ but i doubt it because PowerShell already stated that the issued command failed because StateRepository is actively blocking requests (loosely translated).


Guess i'm back at square one on this one...

Progress!

Instead of searching for answers why sysprep wouldn't shutdown, i choosed "shutdown system" instead.
After this i carried on with the guide (well, actually i went on with this), to where i am now.

There's only one problem left:

When mounting the newly created ISO and doing a test installation, Windows throws the following error after skipping the product key input (the message was in dutch so i have to translate it by myself and/or with help of Google Translate):

"The installation copies (meaning: Windows flavors/editions) that are available for installation couldn't be displayed/listed."

(animated gif, click the image to see it)


I can only click "Ok" and then it sends me back to the "Install now" screen.

Does this error look/sound familiar to any of you?


The iso was created using the following command:

oscdimg.exe -m -o -u2 -lCCCOMA_X64FRE_NL-NL_DV9 -udfver102 -bootdata:2#p0,e,bF:\_\alt.binaries.nl\Win10_1709_Dutch_custom_x64\boot\etfsboot.com#pEF,e,bF:\_\alt. binaries.nl\Win10_1709_Dutch_custom_x64\efi\microsoft\boot\efisys.bin F:\_\alt.binaries.nl\Win10_1709_Dutch_custom_x64 F:\_\alt.binaries.nl\Win10_Dutch_custom_x64.iso

The only modification i've done to install.wim was deleting all indexes except Windows 10 Pro (the planned modifications are saved for when i get this thing to work).


Followed is some DISM commands output:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /capture-image /imagefile:F:\_\alt.binaries.nl\customInstall.wim /capturedir:E:\ /name:"Windows 10 Pro" /Description:"Windows 10 Pro" /compress:maximum /checkintegrity /verify /bootable

Deployment Image Servicing and Management tool

Version: 10.0.16299.15

Saving image
[==========================100.0%==========================]

The operation completed successfully.


C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>[B]dism /get-imageinfo /imagefile:F:\_\alt.binaries.nl\Win10_1709_Dutch_custom_x64\sources\install.wim


Deployment Image Servicing and Management tool

Version: 10.0.16299.15

Details for image : F:\_\alt.binaries.nl\Win10_1709_Dutch_custom_x64\sources\install.wim

Index : 1
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 16.264.664.798 bytes

The operation completed successfully.

Exporting the image to another file also fails:

dism /Export-image /sourceimagefile:F:\_\alt.binaries.nl\Win10_1709_Dutch_custom_x64\sources\install.wim /sourceindex:1 /sourcename:"Windows 10 Pro" /destinationimagefile:F:\_\alt.binaries.nl\new_install.wim /destinationname:"Windows 10 Pro" /compress:max /bootable /checkintegrity

Deployment Image Servicing and Management tool

Version: 10.0.16299.15

Error: 87

An error occurred while processing the command.

Ensure that the command-line arguments are valid. For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

dism.log

Warning DISM DISM Provider Store: PID=7936 TID=12588 Failed to load the provider: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Error DISM DISM WIM Provider: PID=7936 TID=12588 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4705 - CWimManager::InternalCmdExport(hr:0x80070057)
Error DISM DISM WIM Provider: PID=7936 TID=12588 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x80070057)
Error DISM DISM WIM Provider: PID=7936 TID=12588 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2201 - CWimManager::ExecuteCmdLine(hr:0x80070057)
Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070057

*** formatting appears to be messed up? (no new lines) ***. - Apparently the problem seems to be occurring during sysprepping and/or generalizing. Deleting all but one index from install.wim (in no specific order), DISM exporting (with max. compression), integrity checking the optimized image, and using that to install Windows 10 Pro (build 1709) thereafter was succesful. I still don't get it why sysprepping Windows with it results in a non-working installation. AFAIK i'm using the latest Windows 10 Windows Kit (Deployment Image Servicing and Management tool Version: 10.0.16299.15). The only modification i did while in the Windows desktop was adding my own programs (some installed, some added to a folder) and attaching the most recent Hyper-V snapshot as virtual drive using Windows Disk Management, to then DISM capture the modified Windows installation to a new install.wim, and use that for oscdimg to create a new bootable installation disc. But... i still won't give up, it has to work..... some(how/way).

Well, since i seem to be the only person that's active here i'll post another update on the current situation.

Because i literally got fed up with trying and trying, i decided to give the English Windows 10 Pro release a swirl.

Everything was repeated the same way as i did with the Dutch release, but there was ONE major/big difference.

The resulting bootable .iso worked flawlessly!

This could very well be one of those Windows bugs that sneaked into the dutch builds.
Even though it doesn't make sense, because the Dutch release is basically a pre-installed language pack on top of an English build, right? (besides Cortana search bar being enabled in the English build, despite unselecting it during the setup screen)

TL;DR: case closed. Well.. i would still want to know why its messing up the dutch installation. Perhaps a MVP on here can inquiry/inform Microsoft about this problem?

update: Since i wanted to know if the problem was related to deleting all (but one) install.wim index, i left the indexes alone. Well... even without deleting any of those indexes the error still occurred!

Therefore the problem must lay somewhere else. "Where" this may be remains a mystery but i'm expecting it to be fault in the Dutch and/or Non-enlgish versions.