If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Transferring existing Win10 installation
On 07/18/2018 06:27 PM, mike wrote:
On 7/18/2018 2:40 PM, Big Al wrote: On 07/18/2018 05:23 PM, Ed Cryer wrote: tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) A clone of a Windows system is a snapshot of it at a point in time. When you give it the return-to-life spark it just carries on from where it was. And that means a particular hardware configuration, with all relevant driver files, at a particular nanosecond of CPU-processing, all caches as they were etc. Your new system doesn't match the old; hence it will crash. Sorry, pal, but you're forced into option 2; a clean install. Ed And IIRC the digital entitlement license will not work since you changed too many items.Â*Â*Â* MS might be understanding over the phone but I'm not sure. Someone else might talk about the license activation issue???Â*Â*Â* Would entering the old win7 key work?Â* I thought I heard that MS will accept that somehow. I too think you're going to have to do a clean install. You could load it and make an image of the virgin load and then try this from EaseUS https://www.easeus.com/pc-transfer/t...indows-10.html You have nothing to lose and if it fails just put the image back. This may be relevant: https://support.microsoft.com/en-us/...ardware-change Interesting read, so maybe an old Win7 key would work. FWIW, I've experimented moving a hard drive between systems. Detected hardware changes. Seemed to work fine. I can't speak to activation, because all my test systems had win10 digital entitlement. Digital entitlement is a great thing on the surface. I like to know that reloading my system, all I need to do is get it on line and it's activated. Finding that key (not that it's hard to look at a notebook or datafile etc) is just one less thing to worry about. In days of win95 maybe xp I used to move HDs to new systems all the time and get it to find new hardware. Maybe a mobo drivers needed updates but most everything else was simple. I wasn't aware that win10 would do that any longer. Good to know. |
Ads |
#17
|
|||
|
|||
Transferring existing Win10 installation
SC Tom wrote:
"tumppiw" wrote in message news I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) I have done it successfully on two different PC's recently (same version of Windows10), but they were both going from AMD to AMD. I think your biggest problem will be going from AMD to Intel. On both PC's, I cloned the HDD on the old set-up, then put that cloned drive in the new set-up, and W10 booted right up, then searched for new drivers. After about 10 minutes and 1 or 2 reboots, they settled down and continue functioning as they should :-) The only problem I ran into was that one of them booted up in IDE mode instead of AHCI. Took me a few Google minutes to find the simple solution for that. When you do "slmgr /dlv" on each, are the identifiers the same on both ? The other one to compare on the two setups would be "wmic useraccount get name,sid", as normal OS installs would have entirely different number strings for each install. I don't think there is particularly an issue with this, except if you're Cloud oriented and sharing sessions or something and passing info from one machine to another using your MSA. There might be some weird behavior as a side effect. Perhaps if using only local accounts, nobody but Microsoft would know what you've done. I did something like that a couple years ago, and the OS got a bit flustered. I think my side effect, was being asked for my MSA password again, even though the setup was autologin. It wasn't happy about something, and I though it might have been related to some cloning I'd done. What I did was cloned C: on the *same* drive as the original C: , then used EasyBCD to make them both available. Something along those lines. The OS wasn't too happy initially, to boot back and forth between them as a multi-boot, but it eventually settled down. ******* The hottest lead so far to fixing the "sysprep" issue is this one. http://alexappleton.net/post/1597027...-display-media I'm going to give that a try later. I have the tools, I just have to boot up a maintenance OS and do it. Paul |
#18
|
|||
|
|||
Transferring existing Win10 installation
Paul wrote:
I don't think the idea is to transfer the license. The license is a separate issue the OP will have to deal with himself. And fat chance of it working. Assuming some method works(doesn't matter which one, just that it does) for moving an o/s then activation still comes into play. My response was to alert two key points The given that we all know 1. Retail licenses - upgraded from a qualifying o/s and/or Win10 retail media - are transferable 2. OEM licenses are not transferable #1 is pretty straight forward - the activation server knows the underlying license was retail and transferable thus activation almost always succeeds #2 slightly different, the activation server still knows the underlying license was not retail, but OEM, and not transferable thus activation can be problematic. When activation fails the alternatives is 'phone home' based. Those 'phone home' methods are exception mechanisms. Since 1607, MSA was added....and yes, another exception mechanism via the Activation Troubleshooter. The reason why we see successful reports of OEM o/s being transferred is due to an exception being made(either automatically or verbally by a CSA agent). - the exception failure or approval lies on that fine line on abuse or lack or abuse existing, respectively. Use of the MSA(on the o/s prior to any significant hardware change - i.e. that big square board) increases the potential success of an exception being approved(on Retail and, yes, OEM). That MSA linkage is there for a reason...thus anyone considering moving and o/s(regardless of the license type) should take advantage of the additional opportunity the MSA provides. -- ...w¡ñ§±¤ñ msft mvp windows experience 2007-2016, insider mvp 2016-2018 |
#19
|
|||
|
|||
Transferring existing Win10 installation
....w¡ñ§±¤ñ wrote:
Paul wrote: I don't think the idea is to transfer the license. The license is a separate issue the OP will have to deal with himself. And fat chance of it working. Assuming some method works(doesn't matter which one, just that it does) for moving an o/s then activation still comes into play. My response was to alert two key points The given that we all know 1. Retail licenses - upgraded from a qualifying o/s and/or Win10 retail media - are transferable 2. OEM licenses are not transferable #1 is pretty straight forward - the activation server knows the underlying license was retail and transferable thus activation almost always succeeds #2 slightly different, the activation server still knows the underlying license was not retail, but OEM, and not transferable thus activation can be problematic. When activation fails the alternatives is 'phone home' based. Those 'phone home' methods are exception mechanisms. Since 1607, MSA was added....and yes, another exception mechanism via the Activation Troubleshooter. The reason why we see successful reports of OEM o/s being transferred is due to an exception being made(either automatically or verbally by a CSA agent). - the exception failure or approval lies on that fine line on abuse or lack or abuse existing, respectively. Use of the MSA(on the o/s prior to any significant hardware change - i.e. that big square board) increases the potential success of an exception being approved(on Retail and, yes, OEM). That MSA linkage is there for a reason...thus anyone considering moving and o/s(regardless of the license type) should take advantage of the additional opportunity the MSA provides. Thanks for the update. I'm sure Tumppi can profit from it. ******* Purely for it's comedic value, I made some progress on Sysprep. This web page claims the fix for MiracastView can be achieve with an SQL database editor. http://alexappleton.net/post/1597027...-display-media Well, I tried that, and it didn't work. I flipped a single bit which was supposed to imply no account was using the thing, and it still wasn't the solution. I've also been watching Sysprep with Procmon, to catch it making references to MiracastView and there were no direct reads that pointed to any other source. So when the alexappleton.net solution didn't work, I just deleted... C:\ProgramData\Microsoft\Windows\AppRepository\Sta teRepository-Machine.srd ... and the two like-named journal files, which are smaller. I deleted those "offline", not while the OS was running. The next time I booted that clone of Win10, a few items were missing from the Task Bar :-) So this is hardly a perfect solution by any stretch of the imagination. But when I ran %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown it worked! The machine shut down at the end of the sequence. If I wanted, I could take that disk over to this machine, boot up, and the Digital Entitlement on this machine should help to Activate it. I'm not going to do that just yet though. So the message so far, is the information upsetting Sysprep is likely to be in StateRepository-Machine.srd . It's also in other places that don't matter (the Registry). But whatever is in that SQL Database, something other than the single field alexappleton.net suggested ("IsInbox" = 0) needs to be edited. Paul |
#20
|
|||
|
|||
Transferring existing Win10 installation
Paul wrote:
...w¡ñ§±¤ñ wrote: Paul wrote: I don't think the idea is to transfer the license. The license is a separate issue the OP will have to deal with himself. And fat chance of it working. Assuming some method works(doesn't matter which one, just that it does) for moving an o/s then activation still comes into play. My response was to alert two key points The given that we all know 1. Retail licenses - upgraded from a qualifying o/s and/or Win10 retail media - are transferable 2. OEM licenses are not transferable #1 is pretty straight forward - the activation server knows the underlying license was retail and transferable thus activation almost always succeeds #2 slightly different, the activation server still knows the underlying license was not retail, but OEM, and not transferable thus activation can be problematic. When activation fails the alternatives is 'phone home' based.* Those 'phone home' methods are exception mechanisms. Since 1607, MSA was added....and yes, another exception mechanism via the Activation Troubleshooter. The reason why we see successful reports of OEM o/s being transferred is due to an exception being made(either automatically or verbally by a CSA agent). *- the exception failure or approval lies on that fine line on abuse or lack or abuse existing, respectively. Use of the MSA(on the o/s prior to any significant hardware change - i.e. that big square board) increases the potential success of an exception being approved(on Retail and, yes, OEM). That MSA linkage is there for a reason...thus anyone considering moving and o/s(regardless of the license type) should take advantage of the additional opportunity the MSA provides. Thanks for the update. I'm sure Tumppi can profit from it. ******* Purely for it's comedic value, I made some progress on Sysprep. This web page claims the fix for MiracastView can be achieve with an SQL database editor. http://alexappleton.net/post/1597027...-display-media Well, I tried that, and it didn't work. I flipped a single bit which was supposed to imply no account was using the thing, and it still wasn't the solution. I've also been watching Sysprep with Procmon, to catch it making references to MiracastView and there were no direct reads that pointed to any other source. So when the alexappleton.net solution didn't work, I just deleted... C:\ProgramData\Microsoft\Windows\AppRepository\Sta teRepository-Machine.srd ** ... and the two like-named journal files, which are smaller. I deleted those "offline", not while the OS was running. The next time I booted that clone of Win10, a few items were missing from the Task Bar :-) So this is hardly a perfect solution by any stretch of the imagination. But when I ran ** %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown it worked! The machine shut down at the end of the sequence. If I wanted, I could take that disk over to this machine, boot up, and the Digital Entitlement on this machine should help to Activate it. I'm not going to do that just yet though. So the message so far, is the information upsetting Sysprep is likely to be in StateRepository-Machine.srd . It's also in other places that don't matter (the Registry). But whatever is in that SQL Database, something other than the single field alexappleton.net suggested ("IsInbox" = 0) needs to be edited. ** Paul Nice. Thanks for reporting the progress and details. Also, I forgot to mention MSFT is certainly aware there are other variables that come into play for OEM licensed machines(pre-installed by major retailers or pre-installed by a System Builder shop) - End-User takes machine to shop or OEM servicing center (warranty or not) and ends up with a new mobo - Shop(not OEM servicing center) fixes device and uses a VL to reinstall/clean install and activate Win10 instead of using the original sold OEM license/product key In the case of the latter, some of that exception process might also take the form of aiding the end-user to return to a non VL license which once activated replaces the device's and VL licensing info. -i.e. MSFT makes the end-user happy, then separately addresses the more costly issue - the VL abuse by the shop that used the VL. -- ...w¡ñ§±¤ñ msft mvp windows experience 2007-2016, insider mvp 2016-2018 |
#21
|
|||
|
|||
Transferring existing Win10 installation
Paul wrote:
...w¡ñ§±¤ñ wrote: Paul wrote: I don't think the idea is to transfer the license. The license is a separate issue the OP will have to deal with himself. And fat chance of it working. Assuming some method works(doesn't matter which one, just that it does) for moving an o/s then activation still comes into play. My response was to alert two key points The given that we all know 1. Retail licenses - upgraded from a qualifying o/s and/or Win10 retail media - are transferable 2. OEM licenses are not transferable #1 is pretty straight forward - the activation server knows the underlying license was retail and transferable thus activation almost always succeeds #2 slightly different, the activation server still knows the underlying license was not retail, but OEM, and not transferable thus activation can be problematic. When activation fails the alternatives is 'phone home' based. Those 'phone home' methods are exception mechanisms. Since 1607, MSA was added....and yes, another exception mechanism via the Activation Troubleshooter. The reason why we see successful reports of OEM o/s being transferred is due to an exception being made(either automatically or verbally by a CSA agent). - the exception failure or approval lies on that fine line on abuse or lack or abuse existing, respectively. Use of the MSA(on the o/s prior to any significant hardware change - i.e. that big square board) increases the potential success of an exception being approved(on Retail and, yes, OEM). That MSA linkage is there for a reason...thus anyone considering moving and o/s(regardless of the license type) should take advantage of the additional opportunity the MSA provides. Thanks for the update. I'm sure Tumppi can profit from it. ******* Purely for it's comedic value, I made some progress on Sysprep. This web page claims the fix for MiracastView can be achieve with an SQL database editor. http://alexappleton.net/post/1597027...-display-media Well, I tried that, and it didn't work. I flipped a single bit which was supposed to imply no account was using the thing, and it still wasn't the solution. I've also been watching Sysprep with Procmon, to catch it making references to MiracastView and there were no direct reads that pointed to any other source. So when the alexappleton.net solution didn't work, I just deleted... C:\ProgramData\Microsoft\Windows\AppRepository\Sta teRepository-Machine.srd ... and the two like-named journal files, which are smaller. I deleted those "offline", not while the OS was running. The next time I booted that clone of Win10, a few items were missing from the Task Bar :-) So this is hardly a perfect solution by any stretch of the imagination. But when I ran %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown it worked! The machine shut down at the end of the sequence. If I wanted, I could take that disk over to this machine, boot up, and the Digital Entitlement on this machine should help to Activate it. I'm not going to do that just yet though. So the message so far, is the information upsetting Sysprep is likely to be in StateRepository-Machine.srd . It's also in other places that don't matter (the Registry). But whatever is in that SQL Database, something other than the single field alexappleton.net suggested ("IsInbox" = 0) needs to be edited. Paul http://alexappleton.net/post/1597027...-display-media 1) SQLiteBrowser. Open C:\ProgramData\Microsoft\Windows\AppRepository\Sta teRepository-Machine.srd Browse data. Select "Package" table, top line should be perhaps "19" and further over on the right the package name is Miracastbiew. Change the IsInbox field from 1 to 0. Write changes. Exit. The operation cannot be done while the service is running. I did a TakeOwn, and copied the file using a maintenance OS. There are three files, and I turfed the two other files which might be for journaling. The system should create new ones. At some point, you copy back the edited StateRepository-Machine.srd but without the other two files being present. 2) With the target OS booted again, the next step is to put an application manifest back. Find a 15063 C: drive, and copy C:\Windows\MiracastView folder to C:\Windows on the target machine. I keep a set of VHD files with the C: from every original install for reference purposes. And finally, keeping those has paid off. 3) Now comes the satisfying part. Actually being able to remove the blasted MiracastView stub. From an administrator powershell... Remove-AppxPackage Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1 h2txyewy 4) The rest is easy. Or rather, there is a tool to do a bit of housekeeping, where the tool doesn't need Bython. https://blogs.technet.microsoft.com/...sysprep-happy/ https://msdnshared.blob.core.windows...veUserApps.zip administrator powershell: .\RemoveUserApps.ps1 Creates RemoveUserApps.log in the same folder. It is probably removing too much stuff, but at least the method removed a half-present CandyCrushSoda item that I couldn't get rid of otherwise. I would have had to go back to SqliteBrowser, which isn't easy to use when you want to delete something. My system had one easy-to-remove CandyCrushSoda item, but a second one didn't have a corresponding install folder. 5) In administrator command-prompt, prepare target disk for deployment to new system. Computer shuts down if there were no problems doing this. %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown That's a step-wise refinement over my first attempt of just deleting StateRepository-Machine.srd so the system is "blind" to installed materials. I fully expect items are still going to go missing from the Task Bar. HTH, Paul |
#22
|
|||
|
|||
Transferring existing Win10 installation
Paul kirjoitti 19.07.2018 klo 5.17:
tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) Sysprep https://docs.microsoft.com/en-us/win...s-installation Â*Â* "To deploy a Windows image to different PCs, you have to first Â*Â*Â* generalize the image to remove computer-specific information Â*Â*Â* such as installed drivers and the computer security identifier (SID). Â*Â*Â* You can either use Sysprep by itself or Sysprep with an unattend Â*Â*Â* answer file to generalize your image and make it ready for deployment." The following was a Windows To Go example (no Sysprep, runs on same machine). The directory H: in this example, is a Macrium clone of C: with the DiskID changed when the associated VHD is "attached" in Disk Management. https://social.technet.microsoft.com...p-by-step.aspx Â*Â* dism /capture-image /imagefile:G:\install.wim /capturedir:H:\ /ScratchDir:G:\Scratch Â*Â*Â*Â*Â*Â* /name:"AnyName" /compress:none /checkintegrity /verify /bootable Â*Â* # ... various disk preparation steps, like having an NTFS target Â*Â* #Â*Â*Â*Â* for the operation, not shown here. Â*Â* dism /apply-image /imagefile:G:\install.wim /index:1 /applydir:W:\ Some tools for the job, come in Windows WADK, which can be a multi-gigabyte download. Perhaps Sysprep or ImageX would be examples of such tools only in WADK. DISM is available in the OS itself. I don't know how to do all the steps, but there's probably a way to do this. The system will come up with a different SID, and the license key issue will have to be resolved on the new 8600K system. You might be able to buy a key for example, from the Microsoft store, for $100 or $150, and use the key change dialog to enter it. The idea would be, you don't work on C: directly. Some separate read/write volume will need to be worked on separately, as an "offline" thing. In my example, this was H: when I was doing a Windows To Go experiment. But you don't want Windows To Go for this. I suspect some of the same steps are required though. When the new OS comes up, it won't need a license key right away. There should be a 30 day period during which it indicates license status of "Notification", rather than "Licensed". If you succeed in entering a key into the "prepared" OS on the new hard drive, then this command will indicate "Licensed". Â*Â* slmgr /dlv The Sysprep should be handy, for preventing the new OS from looking "too identical" to the old OS. HTH, Â*Â* Paul It looks like I have to go through the PITA of a clean install. I restored my Macrium Reflect backup of C: to the new build (not IN new case yet and with only Intel IGP (i5-8600K @4.0GHz)). Had to use the provided MSI driver disk to get net to work. After about an hour no complaints from DeviceManager. But, unactivated, as you thought. And the key from my new Win10CU box (costed 135eur) isn't good for it. As I said it's an old Win7 (don't remember if OEM or full) upgraded to Win10 and all subsequent CUs. -- ----------------------------------------------------- Thomas Wendell Helsinki, Finland Translation to/from FI/SWE not always accurate ----------------------------------------------------- |
#23
|
|||
|
|||
Transferring existing Win10 installation
Paul wrote: at least the method removed a half-present CandyCrushSoda item that I couldn't get rid of otherwise. Having got rid of it, and before syspreping, would it be worth slipping in [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\CloudContent] "DisableWindowsConsumerFeatures"=dword:0000000 1 to prevent candy crush and similar from getting forced back later? |
#24
|
|||
|
|||
Transferring existing Win10 installation
tumppiw wrote:
...it's an old Win7 (don't remember if OEM or full) upgraded to Win10 and all subsequent CUs. To determine if you have a retail or OEM version, run the following command in a command shell: slmgr -dli |
#25
|
|||
|
|||
Transferring existing Win10 installation
On 07/18/2018 04:23 PM, Ed Cryer wrote:
tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) A clone of a Windows system is a snapshot of it at a point in time. When you give it the return-to-life spark it just carries on from where it was. And that means a particular hardware configuration, with all relevant driver files, at a particular nanosecond of CPU-processing, all caches as they were etc. Your new system doesn't match the old; hence it will crash. Sorry, pal, but you're forced into option 2; a clean install. Ed Not the case. I have transferred existing Win10 installations (many times)into new hardware and it has always re-configured with no problem. It is superior to any previous version of Windows in it's ability to do that. It will not be activated however and a new license will be needed. |
#26
|
|||
|
|||
Transferring existing Win10 installation
philo wrote:
On 07/18/2018 04:23 PM, Ed Cryer wrote: tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) A clone of a Windows system is a snapshot of it at a point in time. When you give it the return-to-life spark it just carries on from where it was. And that means a particular hardware configuration, with all relevant driver files, at a particular nanosecond of CPU-processing, all caches as they were etc. Your new system doesn't match the old; hence it will crash. Sorry, pal, but you're forced into option 2; a clean install. Ed Not the case. I have transferred existing Win10 installations (many times)into new hardware and it has always re-configured with no problem. It is superior to any previous version of Windows in it's ability to do that. It will not be activated however and a new license will be needed. I feel greatly cheered by your comments; and all the others of the same ilk. I didn't know it could be done without lots of trouble, and, not least, problems cropping up one by one for ages after transfer. Experience is the best teacher. If I bought a new OEM box with Win10 installed, and (of course) properly licensed, then it looks as if I could transfer from another box by using simple clone-and-restore completely for free; and problem-free! Ed |
#27
|
|||
|
|||
Transferring existing Win10 installation
On 07/22/2018 12:10 PM, Ed Cryer wrote:
philo wrote: On 07/18/2018 04:23 PM, Ed Cryer wrote: tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) A clone of a Windows system is a snapshot of it at a point in time. When you give it the return-to-life spark it just carries on from where it was. And that means a particular hardware configuration, with all relevant driver files, at a particular nanosecond of CPU-processing, all caches as they were etc. Your new system doesn't match the old; hence it will crash. Sorry, pal, but you're forced into option 2; a clean install. Ed Not the case. I have transferred existing Win10 installations (many times)into new hardware and it has always re-configured with no problem. It is superior to any previous version of Windows in it's ability to do that. It will not be activated however and a new license will be needed. I feel greatly cheered by your comments; and all the others of the same ilk. I didn't know it could be done without lots of trouble, and, not least, problems cropping up one by one for ages after transfer. Experience is the best teacher. If I bought a new OEM box with Win10 installed, and (of course) properly licensed, then it looks as if I could transfer from another box by using simple clone-and-restore completely for free; and problem-free! Ed I have fooled with Win10 drive transfers a lot and have yet to have a problem but like I said you will need to purchase a new license. Interestingly I took an nonactivated drive from a machine and put it in another that had been activated and when I booted up...it was activated. |
#28
|
|||
|
|||
Transferring existing Win10 installation
On 07/18/2018 09:17 PM, Paul wrote:
tumppiw wrote: I wonder what would happen / Can I "clone" my exiting Win10SpringCU (winver=17134.165) from my existing system?? (Windows is a free upgrade from Win7HP) Current system: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, Kingston SSDNow V300 120GB (as C, to my new system: Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200 MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000 240 Gt (nVMe SSD) Transfer or new/clean install (I have a Win10HomeCreatorsUpdate USB-media)??? And I know everybody says: CLEAN INSTALL , but that would be a PITA (as I've had/used/upgraded it since Win10 came out) and I don't have all my softwares install media anymore... I will be changing PSU, case, transferring MY HDDs (Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Rest of new system is: Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will transfer opticalDiscDrive) Sysprep https://docs.microsoft.com/en-us/win...s-installation Â*Â* "To deploy a Windows image to different PCs, you have to first Â*Â*Â* generalize the image to remove computer-specific information Â*Â*Â* such as installed drivers and the computer security identifier (SID). Â*Â*Â* You can either use Sysprep by itself or Sysprep with an unattend Â*Â*Â* answer file to generalize your image and make it ready for deployment." The following was a Windows To Go example (no Sysprep, runs on same machine). The directory H: in this example, is a Macrium clone of C: with the DiskID changed when the associated VHD is "attached" in Disk Management. With XP or Win7 that may be needed but I have never had a problem transferring a Win10 HD to other hardware. |
#29
|
|||
|
|||
Transferring existing Win10 installation
tumppiw wrote:
It looks like I have to go through the PITA of a clean install. I restored my Macrium Reflect backup of C: to the new build (not IN new case yet and with only Intel IGP (i5-8600K @4.0GHz)). Had to use the provided MSI driver disk to get net to work. After about an hour no complaints from DeviceManager. But, unactivated, as you thought. And the key from my new Win10CU box (costed 135eur) isn't good for it. As I said it's an old Win7 (don't remember if OEM or full) upgraded to Win10 and all subsequent CUs. This doesn't deal with your license issue at all, but it shows what an attempted "sysprep" of a previous C: does, when applied to a new computer. https://s33.postimg.cc/w4a8s3pr3/sys...new_system.gif When the new system boots for the first time, it follows the Out Of Box process and requests an account name. It feels like a new OS installation process, but the C: contents contains old content from the previous setup. I made a new account "Chuck Norris" just so I could log in. Once logged into the new system, I could log out and use my previous account. Once in that account, I could see all my personal files were present, and the Win32 icons on the desktop were all present and accounted for. But anything related to the Windows Store is gone. Is that result suitable for other users to use ? I don't think so. I need to use more care when deleting or unprovisioning stuff before Sysprep starts, to be able to do a better job. ******* Winston said in his posts, that using an MSA for the old and new setups, might ease dealing with MS Support regarding moving the OS from the old hardware to the new hardware. That's something I don't plan to test. Not unless I somehow acquired enough money to buy a new computer :-) Paul |
#30
|
|||
|
|||
Transferring existing Win10 installation
VanguardLH kirjoitti 21.7.2018 klo 20.00:
tumppiw wrote: ...it's an old Win7 (don't remember if OEM or full) upgraded to Win10 and all subsequent CUs. To determine if you have a retail or OEM version, run the following command in a command shell: slmgr -dli Response from "slmgr -dli" Name: Windows(R), Core edition Descr: Windows(R) Operating System, RETAIL Channel Partial prod key: xxxxx (I blanked the number) UsagePermission: Information reason for the alert: 0xC004F034 (I'm not sure I've translated these correctly) So it seems I have a RETAIL version. (I guess I have to go through a phone call next week. I didn't) It took about an hour or so but all HW was recognized and installed after I installed network drivers. But anyway I did a new install with my new Win10CU -USBdrive, now I'm only re-installing all apps and programs... At least it feels nice compared to old machine (and a lot quieter) Old machine: ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 @2.73GHz, 4*4096MB (16GB) KHX1600C9D3/4GX, Asus Radeon HD7790 DirectCU II OC 1GB, HDs: Kingston SSDNow V300 120GB,Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Opticals: ASUS DRW-24B3ST Case: CM N400, Antec Basiq430W Some cheap Renesas USB3 2-port card OS: Windows 10 SCu (1803) New machine: MSi B360 Gaming Plus, Intel i5-8600K @4.2GHZ, G.Skill RipjawsV DDR4 3200GHZ @2.666 (m/b limit) MSI GeForce 1050 Ti 4GB LP Kingston A1000 240GB SSD M.2, Samsung HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300 Case VitFenix Shinobi Window, Corsair CS650M OS will be Windows 10 (after activation or full new install Not sure if I transfer the USB-card and ODD to the new one... -- ----------------------------------------------------- Thomas Wendell Helsinki, Finland Translation to/from FI/SWE not always accurate ----------------------------------------------------- -- ----------------------------------------------------- Thomas Wendell Helsinki, Finland Translation to/from FI/SWE not always accurate ----------------------------------------------------- |
Thread Tools | |
Display Modes | Rate This Thread |
|
|