Problem moving Windows 10 to upgraded system

I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
getting Windows 10 100% migrated. Windows did activate via the activation
troubleshooter and most everything seems to be working as it should, but shutdown and
restart won't complete. The screen goes dark, but the PC doesn't stop running. I
have to hit the power or reset button. Also, some installations of drivers, etc.,
hang up. Same with a Windows repair install from inside. I've always heard it's
best to reinstall everything with any major hardware change, but have had pretty good
luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
generation to 7th generation CPU may be too much, though. Any ideas or suggestions
for salvage before I bite the bullet and get started on what will be a 2-3 day job?

Larc

On 4/03/2017 3:13 AM, Larc wrote:
I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
getting Windows 10 100% migrated. Windows did activate via the activation
troubleshooter and most everything seems to be working as it should, but shutdown and
restart won't complete. The screen goes dark, but the PC doesn't stop running. I
have to hit the power or reset button.

Let Window$ Update finish the job. There are big updates after the very
first Win 10 release and then again after builds 1511 and 1607.

Take a look at the Windows Update to confirm.


--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa

Larc wrote:
I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
getting Windows 10 100% migrated. Windows did activate via the activation
troubleshooter and most everything seems to be working as it should, but shutdown and
restart won't complete. The screen goes dark, but the PC doesn't stop running. I
have to hit the power or reset button. Also, some installations of drivers, etc.,
hang up. Same with a Windows repair install from inside. I've always heard it's
best to reinstall everything with any major hardware change, but have had pretty good
luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
generation to 7th generation CPU may be too much, though. Any ideas or suggestions
for salvage before I bite the bullet and get started on what will be a 2-3 day job?

Larc

There's a suggestion here, to run the Windows Update Troubleshooter.
Look in Control Panels, Troubleshooters.

https://www.cnet.com/forums/discussi...down-properly/

If right-click of Start doesn't have Control Panels,
try typing "Control" into the Cortana search box.

Paul

Larc wrote:

I just upgraded the motherboard, CPU and RAM in my main PC and am
having problems getting Windows 10 100% migrated. Windows did
activate via the activation troubleshooter and most everything seems
to be working as it should, but shutdown and restart won't complete.
The screen goes dark, but the PC doesn't stop running. I have to hit
the power or reset button. Also, some installations of drivers,
etc., hang up. Same with a Windows repair install from inside. I've
always heard it's best to reinstall everything with any major
hardware change, but have had pretty good luck not doing that in the
past. Moving from a Z-87 to H-270 chipset and a 4th generation to
7th generation CPU may be too much, though. Any ideas or suggestions
for salvage before I bite the bullet and get started on what will be
a 2-3 day job?


aside
Did you purchase a *retail* version of Windows 10? Or did you buy an
OEM version or get the free upgrade? Those licenses allow one instance
of the license tied to the first computer on which they are installed.
A hardware hash (fingerprint) is recorded so you can reinstall the OS on
*that* hardware. You changed the hardware so a different fingerprint so
it looks like you are trying to install your upgrade/OEM license on more
than one computer.

You get permission to install and run the OS on a single licensed
device. OEM versions (other than those sold in Germany due to a court
ruling there) are locked to the first device on which they are
installed. Retails versions allow migration to a new device (which
changing major hardware components will accomplish) as long as the
licensed instance is removed from any and all prior devices.
/aside

Changing the motherboard results in a huge hardware fingerprint change.
Changing the CPU is changing the brains of the computer, and brain
surgery is a big fingerprint change. Looks like you got lucky.

Did you install the chipset drivers for the new mobo? Are you using
onboard video (its driver should be in the chipset driver package) or a
daughtercard for video? If the latter, did you reinstall its drivers?

On Fri, 03 Mar 2017 14:13:08 -0500, Larc
wrote:

Also, some installations of drivers, etc.,
hang up. Same with a Windows repair install from inside. I've always heard it's
best to reinstall everything with any major hardware change, but have had pretty good
luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
generation to 7th generation CPU may be too much, though. Any ideas or suggestions
for salvage before I bite the bullet and get started on what will be a 2-3 day job?

At one time a fresh Windows install was interesting;- a challenge to
remove everything non-essential for basically stripping the OS into a
fast and effective configuration, reasonably for porting across
hardware platforms.

Sorts of "mini-XP," and not really much past that (SP1), for sorts
such as thumbdrives given for "utilities for technicians" initially to
take a spin on uncharted hardware setups.

Bullets and a 72-hour OS install -- sounds more like Microsoft 10, not
some clunker, for a seriously exclusiveness about licensing fees, and
payment as an integral to allocating continual and ongoing, active
monitoring of the OS.

-
Know thine enemy. -KMarx

On Sat, 4 Mar 2017 03:52:58 +0800, "Mr. Man-wai Chang"
wrote:

| On 4/03/2017 3:13 AM, Larc wrote:
| I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
| getting Windows 10 100% migrated. Windows did activate via the activation
| troubleshooter and most everything seems to be working as it should, but shutdown and
| restart won't complete. The screen goes dark, but the PC doesn't stop running. I
| have to hit the power or reset button.
|
| Let Window$ Update finish the job. There are big updates after the very
| first Win 10 release and then again after builds 1511 and 1607.
|
| Take a look at the Windows Update to confirm.

Updates are always "up to date" on my PCs, especially my main. Thanks, but that's
not the problem.

Larc

On Fri, 03 Mar 2017 15:35:13 -0500, Paul wrote:

| Larc wrote:
| I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
| getting Windows 10 100% migrated. Windows did activate via the activation
| troubleshooter and most everything seems to be working as it should, but shutdown and
| restart won't complete. The screen goes dark, but the PC doesn't stop running. I
| have to hit the power or reset button. Also, some installations of drivers, etc.,
| hang up. Same with a Windows repair install from inside. I've always heard it's
| best to reinstall everything with any major hardware change, but have had pretty good
| luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
| generation to 7th generation CPU may be too much, though. Any ideas or suggestions
| for salvage before I bite the bullet and get started on what will be a 2-3 day job?
|
| Larc
|
| There's a suggestion here, to run the Windows Update Troubleshooter.
| Look in Control Panels, Troubleshooters.
|
| https://www.cnet.com/forums/discussi...down-properly/
|
| If right-click of Start doesn't have Control Panels,
| try typing "Control" into the Cortana search box.

Thanks for the suggestion, Paul. There were problems that were fixed, but
unfortunately none of the fixes did the major stuff.

Larc

Larc wrote:
On Fri, 03 Mar 2017 15:35:13 -0500, Paul wrote:

| Larc wrote:
| I just upgraded the motherboard, CPU and RAM in my main PC and am having problems
| getting Windows 10 100% migrated. Windows did activate via the activation
| troubleshooter and most everything seems to be working as it should, but shutdown and
| restart won't complete. The screen goes dark, but the PC doesn't stop running. I
| have to hit the power or reset button. Also, some installations of drivers, etc.,
| hang up. Same with a Windows repair install from inside. I've always heard it's
| best to reinstall everything with any major hardware change, but have had pretty good
| luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
| generation to 7th generation CPU may be too much, though. Any ideas or suggestions
| for salvage before I bite the bullet and get started on what will be a 2-3 day job?
|
| Larc
|
| There's a suggestion here, to run the Windows Update Troubleshooter.
| Look in Control Panels, Troubleshooters.
|
| https://www.cnet.com/forums/discussi...down-properly/
|
| If right-click of Start doesn't have Control Panels,
| try typing "Control" into the Cortana search box.

Thanks for the suggestion, Paul. There were problems that were fixed, but
unfortunately none of the fixes did the major stuff.

Larc

For hangs, options are limited.

You can check Event Viewer, to see if anything was logged
right around the time of the hang.

There are tools like Process Monitor and WPA (Windows Performance Analyzer).
But to record a shutdown, requires that the log be committed
before the system restarts. If you have to press the power
button, the ETW event file could be lost.

There is simplification as an approach. For example, if the
CPU has graphics, maybe you could uninstall the NVidia video driver,
switch to onboard graphics, and try that. Test whether it shuts
down while using a different graphics solution.

Paul

On Fri, 3 Mar 2017 20:28:49 -0600, VanguardLH wrote:

| Larc wrote:
|
| I just upgraded the motherboard, CPU and RAM in my main PC and am
| having problems getting Windows 10 100% migrated. Windows did
| activate via the activation troubleshooter and most everything seems
| to be working as it should, but shutdown and restart won't complete.
| The screen goes dark, but the PC doesn't stop running. I have to hit
| the power or reset button. Also, some installations of drivers,
| etc., hang up. Same with a Windows repair install from inside. I've
| always heard it's best to reinstall everything with any major
| hardware change, but have had pretty good luck not doing that in the
| past. Moving from a Z-87 to H-270 chipset and a 4th generation to
| 7th generation CPU may be too much, though. Any ideas or suggestions
| for salvage before I bite the bullet and get started on what will be
| a 2-3 day job?
|
|
| aside
| Did you purchase a *retail* version of Windows 10? Or did you buy an
| OEM version or get the free upgrade? Those licenses allow one instance
| of the license tied to the first computer on which they are installed.
| A hardware hash (fingerprint) is recorded so you can reinstall the OS on
| *that* hardware. You changed the hardware so a different fingerprint so
| it looks like you are trying to install your upgrade/OEM license on more
| than one computer.
|
| You get permission to install and run the OS on a single licensed
| device. OEM versions (other than those sold in Germany due to a court
| ruling there) are locked to the first device on which they are
| installed. Retails versions allow migration to a new device (which
| changing major hardware components will accomplish) as long as the
| licensed instance is removed from any and all prior devices.
| /aside
|
| Changing the motherboard results in a huge hardware fingerprint change.
| Changing the CPU is changing the brains of the computer, and brain
| surgery is a big fingerprint change. Looks like you got lucky.

Full retail 8/8.1 Windows Pro upgraded to 10 Pro free and carrying the same
activation rights as the original. It likely wouldn't have activated with the new
hardware otherwise, which it did readily. Thanks, but I was aware of all that going
in and had no concerns about activation. That's not part of the problem. Microsoft
provides a troubleshooter on the Activation settings page designed for some specific
deactivation situations for retail versions, including hardware changes. It was
necessary to log in with my Microsoft account, but reactivation was easy and quick.
No call necessary. I'll now be able to do a clean install with the same hardware in
that PC and it will be automatically activated.

| Did you install the chipset drivers for the new mobo? Are you using
| onboard video (its driver should be in the chipset driver package) or a
| daughtercard for video? If the latter, did you reinstall its drivers?

New INF and ME. Also new LAN driver since it's Intel rather than Realtek that was on
the previous board. Video is a GTX-1050 with the latest NVIDIA driver and it's
working well. All other drivers that should be installed are and are up to date, as
they were before the switch.

Larc

On Sat, 04 Mar 2017 00:01:18 -0500, Flasherly wrote:

| On Fri, 03 Mar 2017 14:13:08 -0500, Larc
| wrote:
|
| Also, some installations of drivers, etc.,
| hang up. Same with a Windows repair install from inside. I've always heard it's
| best to reinstall everything with any major hardware change, but have had pretty good
| luck not doing that in the past. Moving from a Z-87 to H-270 chipset and a 4th
| generation to 7th generation CPU may be too much, though. Any ideas or suggestions
| for salvage before I bite the bullet and get started on what will be a 2-3 day job?
|
| At one time a fresh Windows install was interesting;- a challenge to
| remove everything non-essential for basically stripping the OS into a
| fast and effective configuration, reasonably for porting across
| hardware platforms.
|
| Sorts of "mini-XP," and not really much past that (SP1), for sorts
| such as thumbdrives given for "utilities for technicians" initially to
| take a spin on uncharted hardware setups.
|
| Bullets and a 72-hour OS install -- sounds more like Microsoft 10, not
| some clunker, for a seriously exclusiveness about licensing fees, and
| payment as an integral to allocating continual and ongoing, active
| monitoring of the OS.

I used to average doing 2 clean installs of everything each year, just to get rid of
stray odds and ends and refresh tweaks (never owned an OEM Windows license that
wasn't for a laptop). But I was younger then. It takes me longer now and isn't as
much fun anymore, so I do it only when I'm forced to. And reluctantly then. Wanting
everything "just so" as I do adds to the time I have to spend.

Larc