Meet The Bug In Place Upgrade In Windows 10 20H2

 Meet The Bug In-Place Upgrade In Windows 10 20H2. In preview update KB4586853 which is available for Windows 10 2004/20H2 Via WSUS users, there was a problem about In-Place Upgrade that was reportedly fixed in the update.

But what is the Bug In-Place Upgrade? well on this occasion we will summarize a little and find out more about the problem that is quite troublesome for some of these users.

What is In-Place Upgrade?

As we already know, to upgrade to the latest version of Windows 10 users can use a variety of different steps, for example through Media Creations Tools, Update Assistant, Windows Update, and specifically for Windows 10 20H2, users can upgrade through the Cabinet file "Enablement Package" whose articles you can see on the following page.

By upgrading using some of these options, users can update the version of Windows 10 without losing their data, because the whole thing, both data, applications, and other data are not touched by the upgrade process, so that's called In-Place Upgrade.

Then where's the problem?

However, unfortunately, after the release of Windows 10 20H2, users who upgrade via enablement package will lose important options at the time of in-place upgrade, by no longer being able to save applications, settings, and files, in other words, the upgrade will force to delete all user files.

Exactly as you can see in the picture above, if you are already using Windows 10 20H2 (which you upgraded through the enablement package) and open Media Creations Tools then choose the upgrade option, the option to save personal files and apps, both options can no longer be selected by the user.

Related to this problem is arguably quite strange, and of course, very rarely users experience it, considering that after upgrading, users rarely open the Media Creations Tools application to upgrade again (except maybe later when Windows 10 21H1 has been released).

And in fact, Microsoft itself does not include this bug as the main Bug on the Known Issues page of Windows 10 20H2, but they have indirectly acknowledged this issue in the fixes they made in the KB4586853 Preview update some time ago.

How to Fix Problems

Then how to solve this Bug?, actually by installing Update KB4586853 itself, some users I know report that the problem has been fixed, but to be sure, removing enablement package KB4562830 is the most recommended thing.

By deleting the update KB4562830, of course, users will return to the version of Windows 10 2004.

But don't worry, if your device already supports Windows 10 20H2, the upgrade will be immediately available via Featured Upgrade in Windows Update.

Learning From This?

Arguably with any update method sometimes not very safe for our devices, whether it is through MCT, Update Assistant, Enablement Package files, and even Windows Update itself could bring another problem.

But of the four options above, upgrading through Windows Update is the most recommended, considering that with the presence of upgrades there, it can be said that our device is correctly supporting the version of Windows 10.

Well for those of you who previously upgraded via enablement package, basically there is nothing you need to do unless you want to upgrade again with Media Creations Tools, but of course, in the future, Microsoft will try to fix the problem.

But for those of you who feel that the problem is still a problem and you want to fix it right away, deleting update KB4562830 is something you can do.

So that's a little discussion about the problem of in-place upgrade, hopefully, this article is useful for those of you who have been curious about the problem.

Thank you, hopefully useful.