New
#30
No I did not. I know its link is probably listed here in this forum Ill try to look now...ok I found it..BUT. I am on the Dev Channel so will this Enablement Package ( Download KB4562830 MSU for Windows 10 20H2 64-bit (x64) - 84.9 MB) Work for me? or..can I switch quickly to the Beta Channel and then it would work if I cant be on the Dev Channel?
- - - Updated - - -
Okay again im Running Windows 10 Pro version 2004 Build 21313 and want to get updated/Upgraded to 21H1..
I tried running this enablement package..( Download KB4562830 MSU for Windows 10 20H2 64-bit (x64) - 84.9 MB)
to go from 2004 to 20H2 and when I run it it says its not applicable for my system..? Is there another Enablement Package I can Use that works for my version and Build? Does anyone here know?
yeah IDK I type Winver in search and it says my windows version is DEV
Here is a screenshot showing me trying to install the Enablement Package and IT showing
"The Update is Not Applicable to Your Computer" So since I am on the dev build I cant upgrade to anything Above 2004?
That seems ridiculous. I know I can download version 21H1 and Completely Clean Install and having to Reinstall all my programs and Redo all my settings which sucks A$$.. but I don't wanna have to go that route. Is there anyway to get me to 21H1 from where I'm at? Anyone?
P.S. I Switched to Beta Channel and tried the Enablement package again but that didn't work cause my Version is to High probably.
If you are on 21213 then you have a Dev build. There is no way to move out of the Dev Channel to the Beta Channel except a clean install. Sorry.
Ok thanks I figured as much after doing a little more research. Ill move to the beta channel and then do clean install using newest version iso. Im getting a hefty New upgraded PC in about 2 weeks Ill do it then. Again ty for your answer.
Oh wait one last question..if I Clean Install 21H1 is there a insider channel for it? or Better question your opinion would you stay out of the Insider realm and just go with public release?
Hi there
As people said - running several builds as VM's is probably the easier way.
However there could be another possibility -- how far do your backup archives go -- if you have one from a "standard type" Windows build you could then install the 20H1 on that as an update using the iso created from UUPDUMP.
I always suggest to people before using these sorts of builds (i.e the insider ones) on "production" or day to day machines you should always keep a current Windows standard as a reference backup build - then you can always add / change / mess around with different Windows builds to your hearts content. Disk space is very cheap and the performance of Virtual Machines on current hardware is very good indeed these days. Tools also like Macrium make keeping reference archive backups of Windows builds really easy and quick to do. Finally with the digital licensing these days there's really also no problems with activation issues either by keeping "versions of Windows builds".
All the EULA requires is that you don't run concurrently more than one copy / instance of Windows on the same machine as your product is licensed for.
BTW offered this as an optional upgrade even though I was on the 19042 build not the 19043 builds.
current build upgrading from (i.e before update)
Completed after update
Cheers
jimbo
Last edited by jimbo45; 19 Feb 2021 at 06:09. Reason: added 20H1 screenshot Winver after update