Windows 10: Error message after generalized sysprep
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:
Note: removed whitespace from the error message
2016-08-20 21:13:01, Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist [\??\E:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].
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:\`.
- 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?
Hey everyone, I hope you're doing fine.
Well, I'll keep this short and to the point.
I want to run sysprep on my Windows 10 Pro (x64) PC and I've faced many errors till now which I somehow managed to dodge , Now I've come across another...
Over the past couple of weeks I have experienced a general slowing down of software initiation. Programs that used to be up and running in a few seconds are now taking 20 or 25 seconds to get running. I even see delays in how Firefox operated. I see...
whenever I sign in to my user account I get a blue window with a critical error message......saying Start menu and cortana aren't working ( I have cortana turns off in options anyway ) then it says we will try and fix it next time you sign...
So we're trying to get our first Win10 VM up and running. I downloaded the latest ISo from the Volume License site and installed it on a VM just fine. I ran all Windows Updates as well.
After that I ran Sysprep and choose OOBE,...
Hi there. Using the media creation tool (both usb and ISO) I get an error. Something like "installation has encountered an error during first_boot with sysprep." In not at my toshiba laptop at the moment so the wording may be a little off. Upgrading...