Seems like the registry thing displays only the build # on the desktop which I have used for the past 13 years since XP was on Beta, it's the same info as running winver, couldn't get it to show the actual version #.
Actually, figured it out, just run System Information, it's listed under Hardware Abstraction Layer in the System Summary.
Just for your info:
http://news.softpedia.com/news/windo...d-493408.shtml
Edit
***UPDATE
This morning after this update failed again I decided to try sfc /scannow. I know, I know, we all hate that suggestion.
Well,
it worked! (I HATE that it worked). PLEASE let me know if this did or did not work for you.
Open an Admin command prompt (find option by pressing Windows + X keys) > type sfc /scannow and let it run, reboot when finished > manually run Windows Update > success
(note – CBS.log was FULL of errors.)
https://tweakhound.com/2015/10/01/wi...ed-to-install/
Hi Laevus!
Your welcome and not alone!
Many, many user around the the world have Problems with this CU. I hope MS will fix this soon. Meanwhile im looking around for a practicable solution.
Havent seen it in the dailt driver ( 10547 . )
I have RTM on the other NTFS primary partition I might boot into RTM and see whats up this might be one of the big updates for RTM and it might have some stuff from the last two test bulds for RTM ?
Thank you!
I've just tried with the manual update, but it failed too. I could guess that there is some driver conflict with the update (many Asus owners have problems).
The funny thing is that I've recently restored the sistem, so my Win10 is with the "should be certified" drivers that it comes shipped with.
For the moment being, I will keep WindowsUpdate Service stopped.
I cant even install the update with stand alone installer , seeing the initial install of the kb3093266 BROKE windows update service it no longer starts. so the stand alone installer wont work either...
Cumulative update to RTM worked fine here it restarted twice during the install and then loaded fine did not take long maybe 10 minutes give or take .
I noticed the e mail client task bar icon is the same as before and not the same as the new Icon in 10547 . OTOH maybe that would be a windows store app update thing anyway .
The RTM update seems to run fine on my RTM primary hdd partition ( lucky I guess) . I'm back in 10547 partition ( daily driver ) now .
FYI:
Microsoft implemented Critical Error dialog fixes first on 10547 build, then they pushed those to Windows 10 stable
FYI, current insider build 10547 already contains that fix. “We have fixed a lot of the underlying causes of the critical error dialog Insiders were seeing with Start. “
Quote