-
As mentioned above, the updates has been pulled:
Windows 7/8.1: KB4052234 & KB4052233 has been pulled
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
-
The Store app ‘manifest layout’ bug has been fixed with a store update – and MS rolls out the new store app renaming the store to ‘Microsoft Store’.
See: Windows 10: Store updates with fixes and Microsoft Store
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
In some cases, broken system files are the reason. But my impression is: It’s a bug in Windows 10 V1709.
A workaround may be to set the location to United States. Another workaround, I described within my blog post: Uninstall .NET Framework 3.5. See also http://borncity.com/win/2017/10/19/windows-10-v1709-store-broken-wrong-manifest-layout/
I’ve escalated this issue for Windows 10 V1709 (PC) in MS Anwers – some details are discussed within my blog post
Günter Born – Windows Insider MVP
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
1 user thanked author for this post.
-
Came in this morning to see people frantic as my alpha test group was blue screening machines, following our nightly maintenance cycle, with “inaccessible boot device” error messages being displayed on machines. We believe it’s mostly Windows 10 systems. I’m just starting to investigate. Not every Windows 10 system that patched had a problem, so it definitely may be specific builds. Microsoft is really starting to p*** my off with their lack of QA and cumulative update idiocy. They’ve basically screwed up every single Patch Tuesday cycle this year. I thought past years were bad. I’m just really glad we have an alpha release and beta release process, with an extended window. It’s sad that we have to be so cautious when it comes to their patches. Our process worked, but it’s going to be a nightmare day or two here.
I’ve collected a few details at Windows 10 V1703: Update KB4041676 install issues. This scenario occurs only in WSUS/SCCM, if both alpha and CU has been approved for install (it should have never been released, and admins never should have approved both update types).
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
I’ve written a blog post about the black screen during login on HP machines
Fix for HP’s update KB4038788 login black screen issue
The problem are conflicting registry entries between HP and Microsoft for some .NET entries.Günter Born
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
3 users thanked author for this post.
-
Hours after my post in MS answers forum, a Microsoft employee came back with the following answer:
Done! Working on getting all the docs updated now. I’m told the Patch with the fix is targeted for October.
Let’s see, if Microsoft is fixing this issue in October 2017.
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
1 user thanked author for this post.
-
A German blog reader posted this comment on September 7, 2017, mentions update KB4011039. See also Update KB4011039 causes again Word/Outlook 2016 table bug.
I’ve asked at MS Answers and Technet forum to escalate this issue to MS Office product groups (unfortunately I haven’t the rights to do it by myself as a community moderator in German MS Answers forum).
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
I had not posted it, but media has published an article in early August 2017 …
Günter Born
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
https://borncity.com/win/2017/08/29/windows-10-v1607-mysterious-update-kb4033637/ has been updated (due to the fact, that MS released a KB article). Mr Brian was a few minute to fast – I was just loggin in here to say, that the package has been updated. Our guesses was right (and more precise) than the details MS released today.
@MrBrian: thx for your tip with packed inspector – will give it a try. And thx for your details, you’ve published above.Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
1 user thanked author for this post.
-
Ok, I’ve begun ‘scattered blogging’
After initial post I updated bot (German, English) articles, because the update has been offered on one of my test machines running as a virtual machine.
What I’ve observed, was, that I received after next login a notification to check my privacy settings in V1607.
So my guess is: This update prepares Windows 10 V1607 machines for upgrade to Windows 10 V1703 (Creators Update). That would be the explanation, why not all user are seeing this update. But maybe I’m completely wrong …
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
The purpose of update KB4039871 is clear now – it’s an Update for Monthly Preview Rollup Update KB4034663 – and it addresses an issue with WSUS update metadata processing that can cause some clients to time out with a 0x8024401c error.
See my blog post Windows 8.1: Purpose of Update KB4039871 uncovered
Günter Born
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
@NetDef: So in this case — until I see evidence otherwise — I am pointing my finger directly at PDF-Xchange as the root cause of their problem.
It’s a bit to simple, I guess. If you have read my blog post, not only PDF-Xchange is causing this issue. Also some JAVA applications, Mathlab, IrfanView, ACSee and other tools are coming with redering issues, if ‘desktop composition’ is off.
Don’t tell me, that a JAVA developer has to manage Windows APIs to draw some forms. A German blog reader wrote within a comment:
Dieser Workaround funktioniert. Alternativ lässt sich bei Java-Applikationen auch der Paramater sun.java2d.noddraw=false setzen, um java anzuweisen, die Grafikschnittstelle DirectDraw zu nutzen. Ansonsten wird GDI genutzt, wo scheinbar das Problem liegt.
It mentions a JAVA launch option to force JAVA to use DirectDraw – the the issue is gone. Withount this parameter Windows GDI is used – it seems the issue is within GDI (or WDM).
BTW: Also Office 2013 will have rendering issues on a 2nd monitor. Would you say, that Microsofts Office developers “cheats” that bypass supported API’s?
Just my 2 cents
BTW: The bigger issue with KB 4034664: It breaks again the clients communication with WSUS, as some German blog readers reporting within comments.
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
3 users thanked author for this post.
-
The best I can tell: I received reader comments to my German blog post – and some suggestions I made within German MS Answers forum, that the patches didn’t fix the issues.
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
1 user thanked author for this post.
-
Note – KB4032782 may crash IE 11
I’ve added an addendum to my blog post IE11 printing issues in Windows are fixed (June 2017). Microsoft is aware of this and is researching this problem.
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
Author
