Well, I'm copying the Virtualbox VM from my Windows storage and will try the thing again. Meantime I'm getting close to my main Windows 10 VM finishing - it's on 77% installing. I've created ISO's on this VM before and have the command program open waiting for the link to the esd folder. Hopefully, I will get to do this before I sleep. The other VM should be ready when I wake but given the above problems, I may not like what I'm getting.
Ah well that was a disaster. It was late so left it running. Woke up this morning to a GSOD. A restart sat preparing for ages and eventually took me to a black unresponsive desktop with the message Unable to Locate your Desktop. Restart from that rolled back to 17063, For the moment I've hidden the update.
Woke up as usual at 6am this morning but did't check for updates until 7am as I lost hope last night. Now it's downloaded and awaiting install but as I didn't make usual preparations in time I have to do that first before letting it install, MR backup and system cleanup. Than I make ISO and bootable USB.
There is a bug when choosing to use small buttons in the taskbar:
"Your license will expire soon" problem is still there and thare's no Troubleshoot in Activation panel where it should be:
Maybe because I do have a digital license ?
Otherwise everything works fine.
I let it "percolate" over night and awoke to the PC stopped at a black screen with the Windows logo.
Eventually got it to revert to '63.
Luckily all the files were there to make an ISO and USB drive.
Clean installed. Up an running now.
Defender's 'action recommended' flag showing and got this,
Set Malwarebytes to ' never register' and all green. The link in Defender's Virus and threat protection to open MBAM didn't work and the warning flag still up.
Tried to post this originally in Edge but couldn't upload the image file for some reason.
On a reboot Defender's icon disappeared as described in 'known issues'.
Last edited by Fabler2; 12 Jan 2018 at 06:08. Reason: Additional info
Success! Kinda almost..
Up late do the update. Saw the workaround for the problem I had last build with it hanging at last boot before coming back, then rollback was only option. Have to disable "virtualization" in the BIOS, then it's all fat and happy! It's in the known issues, but not real clear and buried in there. Nasty unwelcome side effect...without virtualization enabled in BIOS, VMware gets rather sick. So I have to toggle the setting if I want to use VMware. And have to leave it off in BIOS while using Insider or it will hang on boot every time, not just the update issue, every boot. Seems to be the only downside I've found. So far....
Quote
