reason: 1-hide from end users, 2- free error in usb: use --> direct wim(s) or FiraDisk tools for iso(s) handle i pus multi version of windows in single usb disk
my problem fixed with KB3213522. Virtual Machine Manager (VMM) --- fixed But i've noticed the privacy settings were on their lowest setting (most comprehensive datacollecting), don't know if that was intended? ok, requested by my customer
The problem never existed, as far as i tested it, it worked fine with the previous CU in VMWare. A customer who wants MSFT collecting the max telemetry and most frequently asking for feedback?
Did a file comparison between the previous CU KB3206632 and the newer KB3213522 (for x64). The only difference between the two 950MB+ files is a change to a 160kb file. The component amd64_microsoft-onecore-i..atedusermode-kernel was updated from .576 to .577. It contains just securekernel.exe, which is related to virtualization-based security, according to the KB page. Of course microsoft-windows-coreos-revision was bumped to .577 also (but it just updates a registry entry).
Visual C++ Redist Installer No update for Visual C++ Redist Installer by burfadel anymore? (after v47) If no, any good regularly updated replacement? Sorry if its not belong here. I don't know where to post it. but burfadel used to post new updates here. Thanks
There's a updated release candidate of the 2017 redists a few pages back, curiously enough they fully replace the 2015 runtimes instead of adding new ones which has otherwise been the standard behavior. (If you have the 2015 runtimes installed those will be uninstalled when you install these 2017 RC runtimes.) I'm not aware of any updates to the 2015 and older runtimes (If the 2017 ones replace the ones from 2015 that probably means those won't be updated further.) but it's possible some security fix or something might have been released for he 2012 or older runtimes since the bundled v47 redist was made and I've just missed that.
I always check event viewer after updates to see if errors appear. Twice the User.dat (Event 4 hive recovery) recovered from an error at boot. Took almost a minute for system to react. It does not always happen but does happen on a regular basis since update. The other is a known DCOM error. It's a permission issues that MS won't fix. I always fix that issue on new install. Error reappeared either because DLL was updated or other.
So dcom is not a new issue (it's even known by msft and prolly by design) and the ntuser.dat corruption error message i didn't even get. As you state yourself it can simply be something local on your system. And even in win 7 after clean install the eventviewer reports similar errors as i show in my clean MSDN install.
Yes for DCOM not the event 5 user.dat issue. Other users have spotted that issue after 594 update. Is it software compatibility or Windows related, too soon to know. Let's just wait and see.