F5F Stay Refreshed Software Operating Systems Yes, you can perform a "Sysprep" on Windows 10.

Yes, you can perform a "Sysprep" on Windows 10.

Yes, you can perform a "Sysprep" on Windows 10.

Pages (2): Previous 1 2
E
Eulfy
Member
122
09-02-2017, 04:31 AM
#11
Your response was incredible, it truly left me amazed. Thank you so much!
E
Eulfy
09-02-2017, 04:31 AM #11

Your response was incredible, it truly left me amazed. Thank you so much!

B
bluefangss42
Junior Member
39
09-03-2017, 07:28 PM
#12
I'm pleased to hear that some users don't advise reinstalling the system after every hardware or disk change. In situations where hardware isn't compatible, tools like Macrium Reflect or AOMEI Backupper (and possibly others) can help. Unfortunately, ReDeploy or similar features are usually only available in paid versions of these programs. On Windows 7, it seems most systems boot normally after hardware updates—even when switching from AMD to Intel boards. Once, I experienced a BSOD and used Paragon Adaptive Restore's bootable USB, which could prepare the existing installation for new hardware in seconds. However, I've learned that this software no longer functions with newer operating systems like Windows 10 (which makes sense given its release in 2010). Overall, hardware changes generally don't cause major issues; Windows typically handles them well. Plug&Play is a reliable option, and the Ghostbuster tool can help keep old drivers intact.
B
bluefangss42
09-03-2017, 07:28 PM #12

I'm pleased to hear that some users don't advise reinstalling the system after every hardware or disk change. In situations where hardware isn't compatible, tools like Macrium Reflect or AOMEI Backupper (and possibly others) can help. Unfortunately, ReDeploy or similar features are usually only available in paid versions of these programs. On Windows 7, it seems most systems boot normally after hardware updates—even when switching from AMD to Intel boards. Once, I experienced a BSOD and used Paragon Adaptive Restore's bootable USB, which could prepare the existing installation for new hardware in seconds. However, I've learned that this software no longer functions with newer operating systems like Windows 10 (which makes sense given its release in 2010). Overall, hardware changes generally don't cause major issues; Windows typically handles them well. Plug&Play is a reliable option, and the Ghostbuster tool can help keep old drivers intact.

F
firecreeper52
Member
124
09-13-2017, 05:01 PM
#13
Intel is targeting AMD, AMD aiming for Intel, Nvidia aligning with AMD to Intel, and Intel connecting with Nvidia to AMD. The Core i7 8th gen will transition to a Core 2 Duo, and vice versa. Assuming BIOS legacy mode was used, this should function. It's important to note the CPU must be compatible with the OS version. If you use Windows 10 64-bit and switch to a legacy 32-bit Atom CPU, it won't work because 32-bit processors can't handle 64-bit applications. Windows 10 relies on 64-bit files for proper operation, so a 32-bit CPU would prevent detection.

Cloning is discouraged. It might seem feasible, but I can't guarantee it will succeed. People often clone systems, which can cause issues later—especially with Windows updates or deadlines like exams or project submissions. It's better to keep systems intact.

Cloning resembles a registry cleaner: it can work in many cases, but problems usually arise after software or OS updates. It's not foolproof. While technically possible, consumer systems are around 97% reliable, and even servers hover near 99.9%. So it's not perfect.

Windows 7 and 8 technically support hardware changes, but reliability has dropped over time. Newer versions are generally more stable than older ones.
F
firecreeper52
09-13-2017, 05:01 PM #13

Intel is targeting AMD, AMD aiming for Intel, Nvidia aligning with AMD to Intel, and Intel connecting with Nvidia to AMD. The Core i7 8th gen will transition to a Core 2 Duo, and vice versa. Assuming BIOS legacy mode was used, this should function. It's important to note the CPU must be compatible with the OS version. If you use Windows 10 64-bit and switch to a legacy 32-bit Atom CPU, it won't work because 32-bit processors can't handle 64-bit applications. Windows 10 relies on 64-bit files for proper operation, so a 32-bit CPU would prevent detection.

Cloning is discouraged. It might seem feasible, but I can't guarantee it will succeed. People often clone systems, which can cause issues later—especially with Windows updates or deadlines like exams or project submissions. It's better to keep systems intact.

Cloning resembles a registry cleaner: it can work in many cases, but problems usually arise after software or OS updates. It's not foolproof. While technically possible, consumer systems are around 97% reliable, and even servers hover near 99.9%. So it's not perfect.

Windows 7 and 8 technically support hardware changes, but reliability has dropped over time. Newer versions are generally more stable than older ones.

J
justin0162
Junior Member
13
09-13-2017, 08:25 PM
#14
I noticed that I consistently choose imaging over cloning, using the latter name for the entire process. This doesn't affect anything since, from my experience, I never encounter issues with updates or unusual behavior. It's all about digital files, not analog. Your JPEG photos remain consistent regardless of how many times you clone or restore them. The same applies to other files. It's just a matter of copying data, and the only downside is using a poor imaging tool. Problems with updates are frequent, whether a fresh install or cloning is involved. Most often it's due to users adjusting settings incorrectly—like turning off services or using basic cleaning software. I don't know the exact number of clones or restores you've done, but I've done them many times. None of the issues you mentioned actually occur, though someone doing it improperly might.
J
justin0162
09-13-2017, 08:25 PM #14

I noticed that I consistently choose imaging over cloning, using the latter name for the entire process. This doesn't affect anything since, from my experience, I never encounter issues with updates or unusual behavior. It's all about digital files, not analog. Your JPEG photos remain consistent regardless of how many times you clone or restore them. The same applies to other files. It's just a matter of copying data, and the only downside is using a poor imaging tool. Problems with updates are frequent, whether a fresh install or cloning is involved. Most often it's due to users adjusting settings incorrectly—like turning off services or using basic cleaning software. I don't know the exact number of clones or restores you've done, but I've done them many times. None of the issues you mentioned actually occur, though someone doing it improperly might.

B
blackshut30
Junior Member
17
09-13-2017, 11:10 PM
#15
the conversation is going well here. I’d like to add my thoughts if I can. I’m on the same side as @GoodBytes regarding the Windows 7 situation. Changing chipsets, even within the same manufacturer, was always risky for 7. Usually it didn’t work properly, often corrupting the boot drive. Once I gave up trying fixes and just installed Windows on a new HDD, I ended up with three drives—Windows was only running on one. After doing a proper sysprep, you could install new parts without losing data. @homeap5 I got really frustrated using cloning tools with older Norton Ghost versions or something similar. Back then you had to use DOS Shell and fdisk just to see your drives, which made the software much easier to use now. Still, I won’t bother with it anymore.
B
blackshut30
09-13-2017, 11:10 PM #15

the conversation is going well here. I’d like to add my thoughts if I can. I’m on the same side as @GoodBytes regarding the Windows 7 situation. Changing chipsets, even within the same manufacturer, was always risky for 7. Usually it didn’t work properly, often corrupting the boot drive. Once I gave up trying fixes and just installed Windows on a new HDD, I ended up with three drives—Windows was only running on one. After doing a proper sysprep, you could install new parts without losing data. @homeap5 I got really frustrated using cloning tools with older Norton Ghost versions or something similar. Back then you had to use DOS Shell and fdisk just to see your drives, which made the software much easier to use now. Still, I won’t bother with it anymore.

X
168
09-22-2017, 11:23 AM
#16
@DudefromHamburg: it’s not just more user-friendly, it actually functions now. I recall Norton Ghost and Paragon. Even Clonezilla seemed overrated. This software can really ruin a bad experience. It felt like a sector-by-sector, mindless copy. Back in the Win98 days, I’d prefer copying drives by overwriting with a solid file manager that keeps all file attributes instead of using such tools. Now it works much better—maybe because the system is more adaptable, but I believe Clonezilla is superior now, since everything gets better over time.
X
xXAguaMarineXx
09-22-2017, 11:23 AM #16

@DudefromHamburg: it’s not just more user-friendly, it actually functions now. I recall Norton Ghost and Paragon. Even Clonezilla seemed overrated. This software can really ruin a bad experience. It felt like a sector-by-sector, mindless copy. Back in the Win98 days, I’d prefer copying drives by overwriting with a solid file manager that keeps all file attributes instead of using such tools. Now it works much better—maybe because the system is more adaptable, but I believe Clonezilla is superior now, since everything gets better over time.

Pages (2): Previous 1 2