No, just a fresh clean install. In fact I've always started from scratch when trying sysprepping again (by installing W10 all over again). I hope the life expectancy of my new SSD isn't compromised too much becausd of this. And Windows 7 was what I used prior to getting the new SSD and I was referring to that with my post. :)
Today's SSD devices are pretty good, you'd need to do this for a couple of years to cause any damage or shorten its life span.
Anyway, your specs only tell you have Windows 10 but not what edition. In case you have Pro edition, here's something for you to consider. This does not work with Home edition, Hyper-V is only included in Pro, Education and Enterprise.
Sysprep tool and Windows image customization in Windows 8 and later work best in Hyper-V. In fact the recommend approach to create a Windows image for deployment is to use a Hyper-V virtual machine as so called technician machine, customize Windows, sysprep and shut down, capture the image and then deploy it to physical computers.
This is of course just a personal and very subjective opinion but in your case I would clean install Windows 10 Pro one more time, enable virtualization in BIOS / UEFI settings, set up Hyper-V and create the install image on a virtual machine.
This tutorial shows how to setup Hyper-V virtualization: Hyper-V virtualization - Setup and Use in Windows 10 - Windows 10 Forums
And here's a complete image customization walkthrough using Hyper-V vm, in your case you could skip everything else except making a simple short answer file to relocate the Users folder: Windows 10 Image - Customize in Audit Mode with Sysprep - Windows 10 Forums
I am afraid I cannot find any clear reasons for sysprep failing even in your latest logs.
Kari
This tutorial has just over 400K views and if you have patience to read the whole thread through, you'll notice that apart those errors and issues caused by user which we have resolved, there are only two or three cases before you that we have not got it working at all.
Again, I am sorry. Take care Matti, see you around here at Ten Forums :)
Terkkuja Suomeen, tekis niin mieli kylmää Karhun kolmosta!
Kari
It's strange but after I move Users folder to drive D: with Method Two recycle bin is lost from Desktop and I can't delete any file (even small) using recycle bin. When I try to delete file I receive something like this:
Hi Kari,
New to Tenforums and first time round moving user accounts as per the Tutorial method.
Did so successfully for a couple of 32bit machines and in my haste created the unattended answer file as "x64" and not "amd64" for the remaining x64bit machines.
Sysprep commenced and the machines has been in a continuous boot loop for 4days.
One had a substantial amount of user docs and the other I removed most of the user docs.
Is the wrong processor indicated in the unattended answer files the culprit, and in that instance, how do I remedy the situation?
Or is the data in the user account folders the issue and I should just let it run its course?
It really is strange, difficult to believe it has nothing to do with relocated Users folder, Recycle Bin for each drive is stored on the root of the drive, not in user profile folders.
Anyway, try this command in an elevated (administrator) Command Prompt to reset Recycle Bin:
Code:rd /s /q C:\$Recycle.bin
This command deletes the non-functioning Recycle Bin. Repeat for each drive replacing the drive letter C: in above command example with each drive letter. When done restart the PC, Windows will now recreate Recycle Bin on each drive.
Kari
Yes, the wrong processor architecture indicator is most probably the cause for your issue. For sysprep it means nothing, Windows tries to enter the OOBE (setup) phase but can't understand instructions in answer file.
Your best shot is to restore a system image, alternatively you could try first if a repair install can fix your issue and let you boot to desktop, then try this method again.
See this tutorial for repair install: Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums
Kari
Quote