New
#130
so i have the touch keyboard problem, have to disable in services.
and the no keyboard in start menu or metro apps.
first time this has happened.
Network driver for killer wireless is flaky, using older driver from Feb.
so i have the touch keyboard problem, have to disable in services.
and the no keyboard in start menu or metro apps.
first time this has happened.
Network driver for killer wireless is flaky, using older driver from Feb.
The Virtualbox VM is failing to update. Keeps saying it needs a reboot after which it just boots 16215. Not exceptionally interested in debugging - I have a VMware WS VM which is on 16226.
I successfully installed 16226 as an upgrade over 16215, after first uninstalling .net 3.5. Problem is that now in 16226 I cannot reinstall .net 3.5 at all.
I've seen the problem with reinstalling .net 3.5 before in Windows...usually a manual install will fix it, something like:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:G:\sources\sxs
Source, of course = drive where your Win10x64 disk is installed (or mounted.) However, did not work this time for me--same error in reinstalling as when I use Windows Update. After installing the 16226 build I ran sfc /scannow and it found and fixed several files successfully, so will try again--have reset WUpdate, too. Still no cigar and no 3.5 reinstall.
...Win update is downloading the .net 3.5 files fine but the install portion fails every time no matter what I do--even manually from the Win10 DVD build 10563, it fails. With Defender turned off, it fails.
No matter what I do I keep getting the same error: 0x800f0922
I've run several different DISM and Powershell commands--even the "ADD Capability" PS commands for it fail with the *same* error. I've opened gpedit.msc and worked and enabled various commands there--makes no difference.
There are a couple of other bugs I've noticed, but I'm going to double-check those and make sure of them before I report them here or to Microsoft.
D3d bugs are still with us--grrrrr-r-r-r-r. Have to report those *again.*
I'm done with it, not gonna spend any more time on it.I did everything I could with VisualC, uninstalled, reinstalled and double checked but exactly same error every time. Just making BOOT usb and will do clean install on second SSD.
For the first time in the past half dozen updates, this one went smoothly and did it on its own. Been a while since that happened. My last update was from a cold install tho.