I have gone back to non-insider, build 17763.253.
The reason I was doing a Repair Install was I was ( still am) having the issue of dropping the Internet connection.
This happens only to this Beelink BT3 Pro mini pc 4GB Ram 64GB Rom.
My other pcs do not have this issue.
Some evidence supporting this theory from @VBF here...
Windows 10 October 2018 Update version 1809 Now Re-Released - Page 114 - Windows 10 Forums...decided to manually Install 1809 from the ISO which I did and let all CUs associated with the update run.
These included KB4476976 Windows 10 v1809 RP Build 17763.288. Obviously this is for the RP wing but Windows Insider Programme is definitely NOT enabled nor has ever been enabled on this PC.
I like my self-fulfilling theory better : Someone upstairs likes me...… :- )
Small comfort to a guy who spent HOURS doing Repair Install and ended up with an unwanted Insider build.
Then spent more time to "roll back" to previous build and …….. Hey, hello, back to square one. I still need to do a Repair Install !!!
Last edited by davidhk; 17 Jan 2019 at 13:50.
@davidhk As Bree suggested, try manually checking for updates and if you are on the Insider Release Preview ring you should get an update that will take you to build 17763.292. If you don't get that then you aren't on the Insider Release Preview ring. However there's nothing wrong with the latest build or the one you are currently on.
It happens again !!!
I went to MCT site, downloaded a copy of ISO to my computer and used it to do a Repair Install.
After completion, I get the insider build 17763.292.
The only thing that could be the problem is that I allowed the process to check for updates during the install.
And the poor sucker once again had to run the Go back to previous build option.
Now back to 17763.253, and the hell with the repair install !!!!!
I suspect that if you DON'T check for updates during the install you won't have that problem.
BTW, if you use the MCT to make a new ISO today it will install 17763.253 anyway (the MCT has just been updated) so there's no point in checking for updates.
Brink's post was 2 days ago. My iso was downloaded yesterday. I shouldn't have to do it again.
I might try a repair install again without checking for updates.
Quote
