Windows 10: Windows10 feature upgrade 20H2 did not allow reversion option

Background
Feature upgrades seem to have a habit of breaking things, usually attached devices. So when I installed win10 earlier this year I created a checklist to check that all the attached devices I use still work, to be run as soon as possible after any feature upgrade was done. Part of the checklist is a check on the reversion option . . . which I have had to use previously.

As a further precaution, I don't upgrade a feature for several months after the upgrade is released - got burnt too many times with prior versions of windows upgrading immediately and then finding there is a bug in it all - that I wait a month or 3 after release (so that the obvious bugs are caught by the eager early adopters, and fixed before the mainstream gets going) before doing it.

What happened with 20H2?
It was generally released in mid Oct 20? I upgraded to 20H2 after 2 monthly patches (nov and dec) on18 Dec. Checking the reversion option, it was not allowed - because it said I'd installed 20H2 on 1 Sep 20 and the 10 day option had elapsed. Several screenshots here:
- the feature upgrade completed details page, which actually has the date of upgrade in the page. I marked it up with the reversion not allowed item. My aim in marking it this way is to expose the dates of upgrade and that reversion should have been allowed.
- the windows version page, which gives the 20H2 upgrade date of 1 Sep 20 - which was the date I upgraded to 20H1 or 2004

So clearly the left and right hand of this 20H2 feature upgrade don't talk to each other. I've feedbacked'd it, but since there isn't ANY mechanism to attach images without going thru an extensive privacy-invading list, I just said a) there should be a way to attach images without that, and b) there were images available if MS wanted them.

Any thoughts on why this snafu happened??? And how to avoid it again?

:)

 

Windows10 feature upgrade 20H2 did not allow reversion option

Background
Feature upgrades seem to have a habit of breaking things, usually attached devices. So when I installed win10 earlier this year I created a checklist to check that all the attached devices I use still work, to be run as soon as possible after any feature upgrade was done. Part of the checklist is a check on the reversion option . . . which I have had to use previously.

As a further precaution, I don't upgrade a feature for several months after the upgrade is released - got burnt too many times with prior versions of windows upgrading immediately and then finding there is a bug in it all - that I wait a month or 3 after release (so that the obvious bugs are caught by the eager early adopters, and fixed before the mainstream gets going) before doing it.

What happened with 20H2?
It was generally released in mid Oct 20? I upgraded to 20H2 after 2 monthly patches (nov and dec) on18 Dec. Checking the reversion option, it was not allowed - because it said I'd installed 20H2 on 1 Sep 20 and the 10 day option had elapsed. Several screenshots here:
- the feature upgrade completed details page, which actually has the date of upgrade in the page. I marked it up with the reversion not allowed item. My aim in marking it this way is to expose the dates of upgrade and that reversion should have been allowed.
- the windows version page, which gives the 20H2 upgrade date of 1 Sep 20 - which was the date I upgraded to 20H1 or 2004

So clearly the left and right hand of this 20H2 feature upgrade don't talk to each other. I've feedbacked'd it, but since there isn't ANY mechanism to attach images without going thru an extensive privacy-invading list, I just said a) there should be a way to attach images without that, and b) there were images available if MS wanted them.

Any thoughts on why this snafu happened??? And how to avoid it again?

 

Windows10 feature upgrade 20H2 did not allow reversion option

I agree.....and don't understand MS position in this matter. What I do know is; MS has a bad habit of this kind of stuff for what ever reason they have for doing it. Where the left hand doesn't know what the right hand is doing. Which makes it so freaking hard to do the simplist of tasks. I found that it mainly happens with every OS upgrade....going all the way back to XP.

Since then...I do like you do and wait 3 months for the OS upgrade to work itself out with the bug fixes and patchs......then I do a clean install. As time and time again users experience horrific OS upgrades.

 

Optional Feature History Windows10

Hi,



Thank you for writing to Microsoft Community Forums.

1. Which version of Windows is currently installed on the system?
   

Developer mode will be installed on the system, if it is enabled in the Settings. Let us go ahead and check the settings to turn off Developer Features.

1. Navigate to Settings > Update and Security > For developer.
   
2. Under Use developer features
   check if Developer mode is checked, Select Sideload Apps from the options, and Developer mode will get unchecked automatically.
   
3. After this steps, check for Windows update, and all the features should be installed automatically.
   

If you still face the issue, reply to this post with answers to the question above.



Hope it helps.

Amit Sunar

Microsoft Community – Moderator