After finish the Upgrade to 16193 I got a Hang and Auto-Restart. Messages was telling that something within the System wasn't correct and need to be repaired. Done that and all seems to be fine now. No Problems with the Graphic Driver anymore, both are shown normal. Also, screen resolution are correct to 1366x768! Problem solved with this new build. Restarted also several times already and all went well! Let see, it will keep that this way!
Does anyone with the system ciphered by vera/truecrypt notes lags compared tu unencrypted? i have a 8600k overclocked and rx470 not very good but think can handle it without problems..
So imaginative these original play on words you guys come up with, must take a super high IQ to come up with such sophisticated humour, I mean who would have ever considered changing Fall to Failed, genius, seriously genius.
Same here running uup-converter, just beeps when trying to select option. Right click worked to paste the folder name beforehand though.
I just upgraded (lazy) with SAM-R's link, all went well, to busy playing with my new Apple iphone 7 Plus to do much else, the pic's and video this thing takes, unreal, 4k.
The funny thing is that I received the changes in that app in build 16188 but without any updates from the store, just from one moment to another change.
There seems to be a pretty bad bug with batch scripts that look for user input in this build - you can't press any keys on the keyboard to answer prompts in these scripts. For instance, I wanted to create a backup installation image using the UUP converter script. I cannot get the script to accept any keyboard (physical or virtual) input. Instead, the system just beeps as if I've pressed an incorrect key. I've tried other batch scripts that use cmd.exe as the backend processor, and have not had any luck pressing keys in any of them. I'm wondering if this is a regression due to a previous build's leftover settings, or if it's an actual bug in the OS. Perhaps they're really trying to kill cmd.exe in this update? Trying to invoke the same scripts within a powershell instance just brings cmd.exe to the party once the script begins executing (which is to be expected, as powershell does not have support for .cmd or .bat files, as far as I know).