Ran a SFC just for grins and no integrity violations this time.
UUPtoISO went well once I found space. With all the newly downloaded files plus the .old file I ran out of space. Installing and running it on my secondary spinner went well.
Defender Security Center's > Device performance & health asked to free up space which I allowed, but theremained on the SC's icon in the tray. Opening SC got rid of it.
Used this and it works. I wasn't on the Skip Ahead ring at all before.For those interested in switching between Skippy and not Skippy:
Skip Ahead to Next Release for Windows 10 Insiders in Fast Ring Windows 10 Windows Update Activation Tutorials
Tested this on a VM. Had Skippy build 16257. Switched to Next version, got 16278. Switching back to Skippy, am now downloading 16353:
Attachment 151253
I wasn't sure if the registry trick would work anymore because although registry clearly shows I had switched back to Skippy, the message in Insider settings is somewhat confusing:
Attachment 151254
Anyway, regardless of that confusing message, switching back to Skippy seems not to be a problem, you just need to change that one value in registry.
Was looking at the size history of the ISOs since "Skippy" was born. 241, I think, was the last before it ever started. 16353 today took a big drop while the RS3_Release from Wed took a big rise. All WIM format.
Well this one went thru like a champ (or was it chUmp) once it got downloaded at 2Mbps. I made ISO and once I hit restart it took 9 minutes to fully usable desktop. So, not counting download time all together half an hour. Sorry Kari but your computer must be very slow. Fast check showed that Run command still doesn't save commands, that's been going on last few builds. Sfc and dism, no problems. Default Printer stayed on but System protection for C: was turned off this time. Many less of custom settings are kept.
Now I wonder what part of Rs4 is in here, nothing in change log, except for auto update for APPs, about that.
A relatively modern i5 laptop with 12 GB of RAM and 7,200 RPM spinner. A lot of other members have reported extremely long upgrades in previous announcement threads.
When upgrade process is running, the CPU usage remains between 15% and 50%, memory usage under 35%, disk usage between 30% and 50%.
Until last ESD upgrade early December, the whole process took less than an hour, from finding the upgrade to restart to upgraded desktop. Since first UUP upgrade never under four hours.
Trying to create ISO's after upgrade. Windows Pro - VMware. Windows Enterprise - Virtualbox.
The host is Debian Sid running the KDE Plasma Desktop
Quote
