Move Windows 10 to a new PC

NavyLCDR said:

\Windows\System32\Sysprep\

I've never bothered with sysprep before a move.

To be fair, Windows 10 is pretty good but not infallible. Problem is if moving drive creates issue, putting drive back on old pc may also fail as drivers will have been changed to reflect new pc.

Always make image backup first.

Kari said:

As Cereberus mentioned, UWP apps make generalizing W10 with Sysprep sometimes difficult. Have to rethink that before making a W10 tut about this process.

Kari

Hi Kari,

This problem only arises for third party apps which are not installed for all users but just a single user.

In most cases, uninstalling them sorts issues. However, sometimes one forgets to remove a certain app, and sysprep bombs out. It is easy to identify the app looking at the sysprep error log. The sysprep error log is pretty clear - see extracts below.

If app will not uninstall using normal uninstall, it can be uninstalled using admin poweshell e.g. for app that causes my sysprep o fail, and refuses to uninstall using normal uninstall :-

Get-AppxPackage 34791E63.CanonInkjetPrintUtility_2.6.0.5_neutral__6e5tt8cgb93ep | Remove-AppxPackage

As sysprep bombs out at first error, so you may have to repeat above ie try sysrep, remove one app, sysprep again, remove second app.

It may be possible to provision the apps so they are available for all users, but I saw conflicting and incomplete info on web, and gave up, deciding it was just easier to delete app and reinstall (could be a problem for some really big apps though).

As an aside, well done on popularity of W7 tutorial, and with a few words of above and updating to Windows 10, it would be a great new tutorial. One minor difference is the way Windows 10 logs in, you end up booting to temporary account first and need to reboot to boot to original account(s).



----------- extracts --------------------------------------------------------------------------------------


2017-05-30 10:24:08, Error SYSPRP Package 34791E63.CanonInkjetPrintUtility_2.6.0.5_neutral__6e5tt8cgb93ep was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2017-05-30 10:24:08, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

cereberus said:

This problem only arises for third party apps which are not installed for all users but just a single user.

I've seen it to happen with native Windows apps like Xbox, Groove and Films & TV. This from only a few minutes ago:


(Click to enlarge.)

Also, some Microsoft's own and third party "suggested" apps cause this. They are not Windows 10 native apps but are shown as suggested. For instance, at least on my numerous installs of EN-GB Windows 10, a third party game Candy Crush Saga will almost always be shown on default Start; the app is not installed but its tile is there, and app folder exists. It will be installed on first run, but already the presence of its tile and folder sometimes causes generalizing to fail.

Screenshot from Start after a clean install. Marked not native but suggested apps can all cause Sysprep to fail even before fully installed.



Minecraft is a good example of a Microsoft suggested app present by default as a tile after fresh, clean install, fully installed on first run but occasionally causing Sysprep to fail even if not fully installed.

Kari

Kari said:

I've seen it to happen with native Windows apps like Xbox, Groove and Films & TV. This from only a few minutes ago:


(Click to enlarge.)

Also, some Microsoft's own and third party "suggested" apps cause this. They are not Windows 10 native apps but are shown as suggested. For instance, at least on my numerous installs of EN-GB Windows 10, a third party game Candy Crush Saga will almost always be shown on default Start; the app is not installed but its tile is there, and app folder exists. It will be installed on first run, but already the presence of its tile and folder sometimes causes generalizing to fail.

Screenshot from Start after a clean install. Marked not native but suggested apps can all cause Sysprep to fail even before fully installed.



Minecraft is a good example of a Microsoft suggested app present by default as a tile after fresh, clean install, fully installed on first run but occasionally causing Sysprep to fail even if not fully installed.

Kari

Yeah I have had one or two similar experiences. In the end, you run sysprep, it fails, you delete culprit and just keep repeating until it works. Does not take that long but is a PITA.

I have never managed to get provisioning working on W10. All guides I have seen refer to old W8 store and they do not seem to work on W10.

I can see why 3rd party apps may choose to be single user only, but not for native Windows apps. A choice would be nice.

TBH, I uninstall pretty much all apps that have an uninstall option immediately on upgrade, so I rarely run into issues above.

cereberus said:

Yeah I have had one or two similar experiences. In the end, you run sysprep, it fails, you delete culprit and just keep repeating until it works. Does not take that long but is a PITA.

When sysprepping an existing Windows 10 installation I usually just remove all UWP apps except Store, run Sysprep and later reinstall those native UWP apps I really want and will use from Store.

In install image creation, booting from OOBE to Audit Mode, this minor issue is not present. Apps will not be provisioned yet, no user profiles exist, Sysprep works as planned.