New
#130
The easiest workaround I know, a solution that works every time is to use a virtual machine as "Get the upgrade" machine.
Using Hyper-V it would go like this:
- Download latest official ISO for your edition and bit architecture
- Install it on a VM. Skip the product key when asked, for this purpose Windows does not have to be activated
- Before opting in for Fast Ring, update VM fully
- When updated create a checkpoint
- Opt in for Fast Ring, restart
- Download upgrade. New fresh installs find it usually immediately
- Make your own ISO from upgrade files, restore VM checkpoint (step 4) to be ready for next build upgrade
- Upgrade physical machines with your ISO; a computer does not have to be opted in for Insider Builds to be able to use them
- When next build is released just repeat steps 6 to 8
Kari
Time to reinstall using the 16179 ISO I created in a VM. Office 365 is complaining about needing to be activated when I still have months left on my subscription. Other signs of instability as well. I do have an image of the current system if I need it.
Given that we are now testing rs3 I think this is the best course of action.
hey guys. i'm new here. reading some of the other threads, and thought i would come look at the latest news in this thread. So it seems like several here are also experiencing the black screen of nothing after updates? Has no one come up with a solution to this yet? I saw what kari wrote, but I don't mess with vm's.
Once again, another version of the fast ring Win10 that errors out at the last moment with a "System Service Exception" error and reverts back to version 170. I have had to put myself on slow ring until Windows finally lets my computer update. The first time since the absolute beginning of the Win 10 beta started that I can no longer update to the latest fast ring's update. All new hardware this spring so there should be no reason for it to fail.
(Tried the registry deletion trick).
Five year old HP laptop with an APU and everything works. Defender 'quick scan' did... after a reboot. Quite disappointing. Seems app managing is helping the old CPU, or APU... whatever its title.
I'm back with a fresh install of Build 16179. Found a significant bug in Mail. Can't create Gmail or Yahoo Mail account. No error messages - the program just hangs. I'm sure I could correct this manually but first I'm going to re-install Office 365 and see what;s with that.
Importing VMs - OK. openSUSE Leap 42.3, openSUSE Tumbleweed, Siduction (these are now updating), Ubuntu Mate, Ubuntu GNOME (both 17.04 - Zesty). Windows Server 2016 Essentials.
Remote Desktop Connection to my Proliant Windows Server 2016 Essentials and the Windows Server 2016 Essentials Hyper-VM.
Having fun.
Interesting how folks are having issues with Office 365 products on this build. No issues on Excel or Word, plan to use PowerPoint this weekend, will see if I am having issues.
Of course, on IP build of Windows, I am also running IP builds of Office, so....