Hi Kari, I have some updates to my post #609: “my laptop is stuck booting into the Admin ID. But at least the user files are no longer on the C-drive”...
The laptop is no longer booting into the Admin ID. There were many folders under D: \Users in the form: Administrator.Desktop-93M44HS and TEMP.DESKTOP-93M44HS etc. I deleted all these. But I still have Administrator, Default and Default.migrated folders under there.
I thought I would make a new system image first before going further. But I received an error message: the backup failed… service cannot be started in safe mode (0x8007043C). In msconfig, I checked that normal start up is selected and that windows back is running. But I had to go to work… Perhaps I need to check for some registry settings later. Or maybe turn safe boot on and then back off…
Any advice would be much appreciated! My new SSD arrived and I would love to get to cloning the c-drive systems while leaving the user files on the D-drive of the old spinning hard disk. But I want to make sure that the base system is stable first. Thank you.
Kari or other thread members - quick bump on my post from last week - any suggestions on ways to resolve the setupact.log error "spopk.dll:: There are one or more Windows updates that require a reboot."?
Code:Error [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
It is actually not an error and will always be shown in logs. It only means that the Sysprep dialog (the one at middle of the screen when you boot to Audit Mode) has not been used.
Then: It looks that your issue is that the answer file is not found. According to the log it should be on the same drive F: where your answer file is told to relocate the Users folder. There's something wrong with that drive assignment.
Although you are not relocating to drive D: as told in the warning box in Method One Step 2, read it and do as told in it to ascertain the drive ID letters will be set correctly. In below quote the warning in question, I've highlighted the part I want you to read:
WarningIf you intend to use drive D: as the location for the relocated Users folder, please read this before proceeding!
Windows "likes" to set the the drive ID letters like this:
- Drive C: > The system drive where Windows will be installed
- Drive D: > First optical drive (CD / DVD drive)
- Drive E: > Second partition on the same disk where the C: is located, or in case that disk only has one partition, the first partition on the secondary disk
Now when you sysprep telling it to move the Users to D: drive, after the reboot Windows might find that the D: is an optical drive and your intended drive D: is now E:, sysprep fails and you have to reinstall.
To be sure you are able to use drive D: for the relocated Users folder you need to set the drive letters manually before the sysprep is run. In Audit Mode you can do this for instance with Disk Management by manually changing the drive letters:
- Change the optical drive letter to something at the end of the alphabet, I use X:
- Change the drive letter of the partition or disk you intend to use for the Users folder to D:
- If the partition or disk you want to use already has a letter D:, change it to something else, close the Disk Management, open it again and change the letter back to D:
See the tutorial at our sister site the Seven Forums: Drive Letter - Add, Change, or Remove in Windows - Windows 7 Help Forums
I recommend to always set drive letters manually to override the defaults but this is especially important for those wanting to use drive D: for relocated Users folder.
Now uninstall any possible third party AV programs (Avira, Avast, Panda etc.). Windows Defender is OK.
When done, change the name of your answer file to unattend.xml and save it to C:\Windows\System32\Sysprep folder.
Now sysprep with this simple command, without the /unattend:
Code:sysprep /oobe /reboot
When sysprep is run, it looks if the Sysprep folder contains a file named unattend.xml. If found, that answer file will be used. The /unattend switch followed by an answer file path and name is only required when Sysprep folder does not contain unattend.xml.
Please try the above and report back.