Information that came out yesterday makes sense. Adobe or Bitstream fonts loaded outside the 'fonts' folder of Windows are the culprit. In my case it probably was Adobe Photoshop that loads fonts in their own folder but puts shortcuts in the Windows 'fonts' folder.
I am still working on a way to fix it from the command prompt since the machine still won't start Windows.
When I've made progress I will post the experience here.
I don't have any problems at the moment. Are the ones with .otf are the ones that should be deleted?
Only if they include a path in the file name. See my post on page 6
Why was this bulletin revised on August 27, 2014? What happened to the original 2982791 security update?
To address known issues with security update 2982791, Microsoft rereleased MS14-045 to replace the 2982791 update with the 2993651 update for all supported releases of Microsoft Windows. Microsoft expired update 2982791 on August 15, 2014. All customers should apply the 2993651 update, which replaces the expired 2982791 update. Microsoft strongly recommends that customers who have not uninstalled the 2982791 update do so prior to applying the 2993651 update.
https://technet.microsoft.com/library/security/MS14-045
Okay, so should I uninstall the previous patch "2982791" (even if it installed fine in the first place, in my case anyway) before applying this new one "2993651"? Or is it safest to wait?
I did that today. No problems. Reboot required after both the uninstall and the install.
My dad installed his update with no problem. He runs on auto so he also had installed the previous update. I believe in the Microsoft statement that this only affects a small number of Windows users.
Well, the benefit of the doubt made me uninstall all the previous "offending" updates offered August 12, 2014 patch Tuesday.
I lived well without them and now, today i installed fine that one...let's see further in the day what could happen!
Edit:
This one is still not offered and my files remains untouched (part of the ones i've uninstalled back then):
-Article ID: 2970228 - Last Review: August 20, 2014 - Revision: 3.0
Update to support the new currency symbol for the Russian ruble in Windows.
Update to support the new currency symbol for the Russian ruble in Windows
I quoted myself just to tell that the:
-Article ID: 2970228 - Last Review: September 2, 2014 - Revision: 5.0
Update to support the new currency symbol for the Russian ruble in Windows.
About this Update:
After you apply this update, the new Russian ruble symbol can be input by using the physical keyboard, Windows on-screen keyboard (osk.exe), or Tablet PC Input Panel (Tabtip.exe) in Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 8, Windows RT, Windows Server 2012, Windows 7, and Windows Server 2008 R2. Additionally, the new currency symbol is added under the Currency tab of the Region settings in Control Panel.
We have defined the new keyboard combination for Russian, Tatar, Bashkir, and Sakha. Check out the Hotkeys Combinations chapter in this article.
This update is released on September 2, 2014.
Status
The following update replaces update 2982791 and resolves this known issue: MS14-045: Description of the security update for kernel-mode drivers: August 27, 2014
-Article ID: 2970228:
Update to support the new currency symbol for the Russian ruble in Windows
Is available as Stand Alone installer at Microsoft Download Center & Automated through the Windows Update, today...!!
Hmm, I wonder if this is related to the Adobe typekit issue that has many businesses up in arms with Adobe Creative Cloud? Perhaps another black cloud for computing over the cloud?
Regards,
GEWB
It tooks a while downloading from automated WU but I've installed that Kb Article ID: 2970228, fine.
I do not think anybody will or could have an issue with that one because they did patched only the .DLL this time, and not the Win32k.sys.
Quote