Not when you use abbodi1406's esd>iso v28 (current release): 15046.0.170224-1700.RS2_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO @atari800xl: Doet mijn vrouw al
It was nice to see Bat.1 today, I hope he's off needless strike, I miss his Cam Girl Jokes As much as I did not want to even joined Insiders on test computer
I used "adguard's esd-decrypter" for esd to iso and my iso name end up being "15046.0.170224-1700.RS2_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US"
Strange Windows Updates is. I was on Build 15042 and it downloaded UUP files but come up with error message few times when Windows tried to install it. Then my Windows Update ended up downloading the esd file and it updated with no problems doing it from esd.
Clean install and it is working fine. It still shows v1607 in winver. Was this supposed to show up as v1703?
in this build let's say bye bye to the old Windows Defender UI, but in the new Windows Defender UI a new small bug was introduced xD if you do a quick scan and close the new UI, the quick scan is cancelled instead of continue running in background, lol xD