Windows 10: Every time I run the Sysprep, then I restart the Windows, a error message will display in...

May I ask if anyone have idea for the situation below?Every time I run the Sysprep with generalize to make a image and reboot the Windows, the message will be pop up in the BIOS page."Windows cannot find c:\program files\.exe...make sure you typed the name correctly"Then I press ok, and reboot the PC, everything is ok. It will not show anymore.However, when I run Sysprep again, the errors will be occurs again.I have search the keyword XCVault.exe in Registry and tried to install and uninstall the PDF-Exchange editor the .exe file is a license activation file related to PDF-Exchange editor,

:)

 

Error message after generalized sysprep


I have 2 exactly the same configured Windows installations, both 32bit and 64bit. These Windows installations are referring to other other drives for specific settings, such as:

* The users folder is redirected to the `U:\Users` drive
* Some programs are installed on the `P:\` drive.

The OS is installed on the `C:\` drive.

For constantly testing these configured machines with the settings, I used a non-generalized sysprep, and booted back into the same virtual machine (I did not test it on another machine yet).

These non-generalized syspreps into OOBE worked perfectly.

When I was done configuring the machines how I wanted, and knew they both worked in a non-generalized sysprep. I sysprepped them with the generalize option on.

From here I made a WinPE boot environment and captured an image of the `OS` partition (`C:\`) and the `PROGRAMS` partition (`P:\`).

Now I made a new virtual machine and booted into WinPE with the device connected where the captured images we're on.

Here I created the following (needed) partitions using diskpart:





These are the partitions that correspond to the sysprepped machines that worked without generalize. The system partition was just a try, I also tried doing it without it.

After having created the partitions I applied the images to the corresponding disks (`C:\` -> OS partition, `P:\` -> Programs partition). This by using the DISM /apply-image command. I am sure I choose the right index of the .WIM file.

Then I used the `bcdboot C:\Windows /s C:` for creating the boot files, this successfully worked.

After restarting the machine using the `exit` command and not booting into WinPE, I got the following error message.





When opening up notepad via SHIFT + F10 and opening the `\Windows\Panther\setuperr.log` file, there is this line:

Code:

Code:

2016-08-20 21:13:01, Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist [\??\E:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].

Note: removed whitespace from the error message

Also, when I open up notepad and check for my drives when opening a file, there are all kind of drives I did NOT make in WinPE.






The only thing that is correct is the `C:\` drive, the PROGRAMS drive should be `P:\` and the USERS drive should be `U:\`.


Questions

• Where did these random drive letters come from? I already set them

in WinPE before starting the Windows installation.

• How can I make my generalized sysprep work with these settings?

 

Windows 10 - unable to build a sysprep image without OOBE

After the administrator details were removed, the system gave a blank error message followed by an error message saying - Windows could not complete the installation. To install Windows on this computer, restart the installation.

Steps I followed:
1. Install Windows without connecting to the internet
2. Login into Audit mode
3. Close sysprep pop-up. Launch Command prompt. Navigate to the sysprep folder and give the sysprep command.
4. Restart

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

Failed to sysprep and capture Windows 10 Fall Creators 1709

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh