I thought this article was interesting and wanted to implement it:
https://www.ghacks.net/2018/06/21/ch...ture-upgrades/
However it failed for me. Anyone know why it might not have worked and I got an error message? TIA.
Your screenshot shows you are on build 16299.431. That's version 1709. Brink's tutorial on this says...
Set Number of Days can Go Back to Previous Version of WindowsStarting with the Windows 10 April 2018 Update v1803, new DISM commands have been added...
So all you have to do to get it to work is upgrade to version 1803
Thanks for the quick response. Obviously you do not know why someone else did not point that out since I believe that many eyes look at those articles and in addition why do you think he was successful in his example running the command "DISM /Online /Get-OSUninstallWindow" and he was able to get results in his command window. Thanks.
>So all you have to do to get it to work is upgrade to version 1803Your screenshot shows you are on build 16299.431. That's version 1709. Brink's tutorial on this says...
Set Number of Days can Go Back to Previous Version of Windows
So all you have to do to get it to work is upgrade to version 1803
HOLY CRAP! No thank you!!! But thanks so much for pointing out the error of my ways : )
Actually, it doesn't work on 1803, but it does work on Insider Previews, to wit:
Here's what I get from 1803 right now:
And here's what I get from the Insider Preview, Build 17692
It will be part of the OS after 1809 comes along.
HTH,
--Ed--
Hello Ed,
That error message in 1803 indicates that the previous version has been deleted, and there's currently not a previous version to go back to.
Set Number of Days can Go Back to Previous Version of Windows | Windows 10 Tutorials
I tested that by doing a repair install of 1803. Until I used Disk Cleanup to remove the previous version the DISM commands worked as described in the tutorial.That error message in 1803 indicates that the previous version has been deleted, and there's currently not a previous version to go back to.
Oho! Thanks @Brink and @Bree: good to know that the command is sensitive to the presence or absence of Windows.old (previous version). Because I ALWAYS run an image backup (Macrium) before an upgrade and then Disk Cleanup afterward, I don't keep Windows.old around on production OS version machines. Just so happens my MS Surface hadn't been cleaned up yet, so it responded as it expected to show/change the time window. I was unaware it worked like that, so I just learned something. Thanks again,
--Ed--
Quote
