Starting the upgrade of the physical machine - and its proceeding rapidly
It's now starting the downloading phase. Just saw an article posted here on so-called "bashware" which is malware infecting the WSL. This sucks badly. I suppose I can try installing a Linux AV and start a scan when the bash command is called. But I must study this further.
That was resolved with upgrade to next build, I guess repair install had done the same. Until the upgrade, I found no solution which forced me to unlink the Microsoft account in question from OneDrive. Checked a few times linking the account again, issue remained, unlinked again but after the upgrade it was then back to normal.
Skippy is still shown as 1703. it's the non-Skippy that was changed to 1709.
[
Skippy is still shown as 1703. it's the non-Skippy that was changed to 1709.[/QUOTE]
Interesting.
Having problems upgrading the physical machine. At least one of the error messages involved not having enough disk space.
With 28 GB free and only 67% of the disk used this is ridiculous. I made an ISO from a VM install and am debating a clean install. Very irritating.
This is why suggested a switch to bypass the creation of the windows.old creation.
There is plenty of free space.
Volume in drive C is Windows 10 IP Build 16353 Serial number is 5afa:3961 85,349,371,904 bytes total disk space 57,289,617,408 bytes used 28,059,754,496 bytes free 67.1 % in use
OK. Clean install of 16362. I wish somebody from Microsoft could explain why they must want to save a copy of the old build when I (and I assume I'm not alone) will just run disk cleanup immediately anyway. Anyway the install went perfectly and I like the feel of the build. The graphics card was even updated during the install itself - that's a first.
Quote
