Some important dumb question

[omg]

so actually i have 2 questions:-

1- Can i reactivate my oem windows 10 pro license after changing motherboard via linking with microsoft account??

2- Can i use backup software like minitools or Ubackup etc. for changing my cpu and motherboard without reinstalling my windows 10??

[SansVarnic]

38 minutes ago, omg said:

1- Can i reactivate my oem windows 10 pro license after changing motherboard via linking with microsoft account??

You can, but it may take a phone call to Microsoft if it doesn't on its own. Today your license is linked to your MS Account and the Motherboard it was installed on. Just link your account and see what happens, if this doesn't work call MS support and have them reset the license, they have don't it before in cases when a faulty board is replaced.

38 minutes ago, omg said:

2- Can i use backup software like minitools or Ubackup etc. for changing my cpu and motherboard without reinstalling my windows 10??

That I cant answer, never used either software but it is possible theoretically.

[homeap5]

You don't must use any software. After hardware change just boot your current system.

 

I wrote this many times, but maybe a little explanation why it's possible and why it works even with previous OS including XP, but was more problematic then.

 

System load basic stuff at the beginning. It loads also drivers for your motherboard, hdd controller etc. It compares your hardware id to stored in registry and if anything changes (including when you add new device) - installs needed drivers (or use ghosted ones if they're already installed, but not used).

 

First you should think is - how system can load anything if it needs drivers to load stuff? Interesting, right? Even your sata controller needs to be load from the same device system wants to control. It's vicious circle, isn't? No, not really - system has basic drivers that works before proper dedicated drivers are loaded and every controller is compatible at very basic level with that. It's not maybe very good explanation, but it how it MUST work if you think a little - how system can load anything and start if you have no drivers for anything load and yet these drivers are loaded anyway.

 

Anyway, back then, when Microsoft invented plug&play, it works basically the same as today. Except detection order. It has more sense to load, for example, motherboard drivers and better dedicated sata drivers first, then load system using updated and probably faster drivers. But that creates problem, because when different drivers was loaded first, you may get BSOD when you switch motherboard. Not always, but when driver was much different, it was happen.

 

If you have any experience with previous Windows installation and changing motherboard, you may notice that XP, Vista or Win7 load everything, including desktop, then run plug&play procedure to detect new hardware. And you can see progress in window on your desktop (if you open it from tray). Your system was already loaded so you can browse internet (for example) or do anything (except lot of things do not work yet, because system still loads drivers and adjusting to new hardware). So, if you're lucky - it works. If not, you must use tools like Paragon Adaptive Restore to Adjust OS to prevent BSOD.

 

Win10 has no new revolutionary plug&play system. If you look how it works when you change motherboard, you should figure out what is changed. Now system just check your hardware ID and detects new hardware BEFORE it load current (and that means "previous" if you change motherboard) configuration. That means no matter how SATA controller do you had beforfe, or motherboard, or processor - drivers for that hardware is not loaded UNTIL Windows ends detection and installing new hardware drivers. And that change is in fact revolutionary - now every user can change hardware without fixing anything and/or preparing system for hardware change.

 

So, long story short - it's all hardware ID, informations stored in registry and plug&play. Nothing really changes for years except detection order and loading drivers order. Microsoft just need loong time to made it better (but who knows, maybe if order of loads was like in win7, new system will load 1 or 2 seconds faster using better drivers from the beginning - lot of people still believes that clean install is the only way).

 

Someone may explain it better, more technical and more proper.

 

The biggest problem with all advices like "you must reinstall system" etc. is that people repeats one after another the same myths. And it's because people rarely uses common sense - is it really that hard to plug your old drive and boot? Especially if you was prepared to install new system anyway? How long it will take to check? 30 seconds?

 

[omg]

On 6/8/2020 at 3:37 AM, homeap5 said:

You don't must use any software. After hardware change just boot your current system.

 

I wrote this many times, but maybe a little explanation why it's possible and why it works even with previous OS including XP, but was more problematic then.

 

System load basic stuff at the beginning. It loads also drivers for your motherboard, hdd controller etc. It compares your hardware id to stored in registry and if anything changes (including when you add new device) - installs needed drivers (or use ghosted ones if they're already installed, but not used).

 

First you should think is - how system can load anything if it needs drivers to load stuff? Interesting, right? Even your sata controller needs to be load from the same device system wants to control. It's vicious circle, isn't? No, not really - system has basic drivers that works before proper dedicated drivers are loaded and every controller is compatible at very basic level with that. It's not maybe very good explanation, but it how it MUST work if you think a little - how system can load anything and start if you have no drivers for anything load and yet these drivers are loaded anyway.

 

Anyway, back then, when Microsoft invented plug&play, it works basically the same as today. Except detection order. It has more sense to load, for example, motherboard drivers and better dedicated sata drivers first, then load system using updated and probably faster drivers. But that creates problem, because when different drivers was loaded first, you may get BSOD when you switch motherboard. Not always, but when driver was much different, it was happen.

 

If you have any experience with previous Windows installation and changing motherboard, you may notice that XP, Vista or Win7 load everything, including desktop, then run plug&play procedure to detect new hardware. And you can see progress in window on your desktop (if you open it from tray). Your system was already loaded so you can browse internet (for example) or do anything (except lot of things do not work yet, because system still loads drivers and adjusting to new hardware). So, if you're lucky - it works. If not, you must use tools like Paragon Adaptive Restore to Adjust OS to prevent BSOD.

 

Win10 has no new revolutionary plug&play system. If you look how it works when you change motherboard, you should figure out what is changed. Now system just check your hardware ID and detects new hardware BEFORE it load current (and that means "previous" if you change motherboard) configuration. That means no matter how SATA controller do you had beforfe, or motherboard, or processor - drivers for that hardware is not loaded UNTIL Windows ends detection and installing new hardware drivers. And that change is in fact revolutionary - now every user can change hardware without fixing anything and/or preparing system for hardware change.

 

So, long story short - it's all hardware ID, informations stored in registry and plug&play. Nothing really changes for years except detection order and loading drivers order. Microsoft just need loong time to made it better (but who knows, maybe if order of loads was like in win7, new system will load 1 or 2 seconds faster using better drivers from the beginning - lot of people still believes that clean install is the only way).

 

Someone may explain it better, more technical and more proper.

 

The biggest problem with all advices like "you must reinstall system" etc. is that people repeats one after another the same myths. And it's because people rarely uses common sense - is it really that hard to plug your old drive and boot? Especially if you was prepared to install new system anyway? How long it will take to check? 30 seconds?

 

So u mean to say windows 10 can load on a dissimilar hardware alright after auto installing that hardware drivers??btw i m changing my processor from intel to amd but really dnt wanna reinstall win 10.

[homeap5]

43 minutes ago, omg said:

So u mean to say windows 10 can load on a dissimilar hardware alright after auto installing that hardware drivers??btw i m changing my processor from intel to amd but really dnt wanna reinstall win 10.

No, I changed dozens of systems without reinstalling. I have my own win10 changed from i5 3gen to i7 8gen and my wife has Ryzen 5 3600 (changed from 4th gen i5). As I said - system change drivers, change hardware ID and when finish adjusting (and restart) load only necessary drivers that fits your new hardware.

 

You'll be fine. And if something wrong happens (don't know what) - just ask.

 

There is also tool called Ghostbuster that you can use after if you really want to remove unused (ghosted) drivers. If you want to feel more fresh or whatever. It's not necessary, but it's up to you.

[omg]

43 minutes ago, homeap5 said:

No, I changed dozens of systems without reinstalling. I have my own win10 changed from i5 3gen to i7 8gen and my wife has Ryzen 5 3600 (changed from 4th gen i5). As I said - system change drivers, change hardware ID and when finish adjusting (and restart) load only necessary drivers that fits your new hardware.

 

You'll be fine. And if something wrong happens (don't know what) - just ask.

 

There is also tool called Ghostbuster that you can use after if you really want to remove unused (ghosted) drivers. If you want to feel more fresh or whatever. It's not necessary, but it's up to you.

kk tyvm for solving my issue