Transplanted hard drive not detected Sleep mode

[johnrobert]

Transplanted a hard drive with Win 10 from a dead desktop into a newer donor I thought that’s great I don’t have to reinstall everything I notice in power settings there is no sleep for computer only display.

I enabled in advanced settings hibernate, but I have to press power to wake up and its almost the same as a restart

Is there any way of making it detect hardware or maybe doing a Win 10 upgrade might be the best option.

 

[Porthos]

Sleep is heavily dependent on Video drivers. Check them.

 

[Porthos]

I thought that’s great I don’t have to reinstall everything

Also, any software that is motherboard dependent for licensing will need to be reactivated. MS Office is one of those.

Win 10 upgrade might be the best option.

That or a repair install if it was already up to date is never a bad idea when transplanting a drive to new hardware just in case. Saves possible issues down the road.

 

[johnrobert]

Thanks, that's what I will do as I notice it will not update

Should have done a N&P

 

[Porthos]

Should have done a N&P

Personally, I prefer them but there is always someone with programs they cant reinstall. But with more and more software dependant on hardware-based licensing, It can get complicated and we get blamed if everything does not just work as before and we might end up spending unpaid time fixing it if even possible.

 

[Markverhyden]

If it boots why not try syspreping it.

 

[Diggs]

If it boots why not try syspreping it.

I've got to admit, even though I go back to DOS command line days I'm not familiar with all the capabilities sysprep. The geek in me is peeked. I need to do my homework.

 

[johnrobert]

I uninstalled video driver in device manager and deleted driver then windows reinstalled video now sleep shows up
deleted everything in software distribution now its auto updating to 20H2
no licenses to worry about.

Thanks again

 

[Markverhyden]

I've got to admit, even though I go back to DOS command line days I'm not familiar with all the capabilities sysprep. The geek in me is peeked. I need to do my homework.

At it's core sysprep is supposed to remove settings, etc that are related to the local installation. So it should be a simple way to "cleanup" an installation before moving to new hardware. Of course the licensing is still in effect. So you can do that with VLK and Retail. While not specifically cleared I'd think you could do this on OEM boxes as longs as the same OEM and the new box is licensed for the same version, Home or Pro, as the old version. Another item I've noticed but not played with. With W10 it does not roll back major upgrades. So if it originally shipped with 1703 and it's now at 2004 it'll stay at 2004.

Last year, during the underwhelming amount of work I had, I spent a good bit of time playing around with it using various old machines lying around. While W10 seems to take new hardware platforms pretty well this might be a simple step to make life easier. Of course the downside is you'll loose added programs after syspreping.

 

[Porthos]

I uninstalled video driver in device manager and deleted driver then windows reinstalled video now sleep shows up
deleted everything in software distribution now its auto updating to 20H2
no licenses to worry about.

Thanks again

I knew the video was the sleep issue.

 

[NJW]

Of course the downside is you'll loose added programs after syspreping.

In the olden days (Windows 7), I recall installing common programs (for all users, not just the logged in account) before sysprep and they were all there in a new installation. Has that changed? (Windows 10 + SSD has made sysprep pretty much obsolete for me these days.)

 

[Markverhyden]

In the olden days (Windows 7), I recall installing common programs (for all users, not just the logged in account) before sysprep and they were all there in a new installation. Has that changed? (Windows 10 + SSD has made sysprep pretty much obsolete for me these days.)

To be honest I didn't experiment with that. I just took a old W7 machine and manually cleaned out programs before playing with it. Maybe I'll take a gander later this week. My understanding is that was what audit mode was for.

 

[NviGate Systems]

Yeah, you use Audit mode to add any apps. HP used to use Audit mode to perform scripted installs of all support software for a laptop.

However, you don't add any software that relies on a unique SID, as it can cause issues in a large LAN environment.

Audit mode would be where I would add any LOB App.

I don't know if it still applies but you can't sysprep after you have done a major software release. So if you started with Build 10240 and then upgraded to another build, sysprep is no longer available.

Also, in Windows 8/8.1 updating App Store Apps caused sysprep to fail. I believe this is because App Store Apps are user based and are not system wide apps.