Windows 10: Booting sysprep cloned image to spinning dots

hi.

So I have imaged a Windows 10 HE that I have sysprep /generalize to OOBE on virtualbox.

And written back that image (YES disk image not vm disk, don't ask me how) to my HP Stream 10 netbook.
After fixing issue with the boot process, it boots now to the HP logo and the spinning dots.

I am assuming Windows 10 is starting to load but fails ?

What could be the issue ? given that it is a sysprep generalized image, I am guessing it should be ok for the drivers, right ? What step of the boot process is it ? Why is it stuck in it ?

What could the problem with those spinning dots and how to fix it ?

:)

 

Disable Superfetch permanently

We use Windows 10 version 1703 with underlying datastore as SSD for our performance activity.

High CPU utilization was seen after the completion of workload, as confirmed from task manager cpu hike was caused by Superfetch.

The Superfetch service was disabled and stopped from services.msc and same updated in regedit on Golden image. When the base image was used to clone new windows machine, Superfetch was enabled and running on these new cloned machines.

We do sysprep for cloning of new machines and looks like sysprep enables the service.

Is there any permanent way which can be used to disable Superfetch on Golden Desktop.

Please assist.

Thanks in Advance,

Anuradha

 

windows 10 does not load, stuck at preparing automatic repair, ISO does not work just windows logo and spinning dots , any fix ?

I have tried several times. I have changed the boot order in the bios and have gotten to boot from usb stick , but only get the windows logo and dots spinning in a circle. The iso does not do anything other than give the windows logo and keeps on with the
spinning dots. Same with preparing automatic

repair, I get the HP logo with preparing automatic repair and the spinning dots and it does nothing else does not go to diagnosing your pc. I have tried booting from dvd with ISO on it and get nothing but HP logo and spinning dots.

 

this time I really fixed those boot issue by using the correct tool. I mean I booted a live cd and run "Repair computer", command prompt bootrec /fixboot and bootrec /rebuildbcd.
That's it

sorry for the noise.

You could delete this thread if you want