Bork Tuesday, Any Problems Yet?

Patch Lady – my response
August 04, 2018
https://www.askwoody.com/2018/patch-lady-my-response/

 

Microsoft’s Poor Reply to Open Letter on Windows 10 Update Experiences
https://www.bleepingcomputer.com/ne...open-letter-on-windows-10-update-experiences/

 

I installed all Windows 7 and Office 2010 updates. So far I encounter minor problem with IE. Sometimes it doesn't open webpage on first try. After reloading it page opens. Funny thing is that on refresh it switches from x64 to x86 version of IE. I wonder what they broke this time.

 

I never post in this thread, usually. But, just for nostalgia on my old XP desktop in this particular snapshot, this still works for me.

 

No problems here too...

 

Yes, I too seem to have some kind of problem on Win 7 Pro 64 bit with IE11 (Dutch).
At the moment only updated via MS Catalog:
- Security Only Quality Update for Windows 7 for x64-based Systems (KB4343899)
- Cumulative Security Update for Internet Explorer 11 for Windows 7 for x64-based Systems (KB4343205)

What is happening, I'm not sure.
Other MS updates not yet done. They have to come later when I have time (due to circumstances).

 

Or here x3 machines.

 

Ghacks and Woody say issue with third-party software related to missing oem<number>.inf file still exists for monthly W7 rollup and July .net bugs have not been fixed yet for W7 and W10.

 

Updated. Windows 10 Home. No issue from what I can see.

 

Do you both still see issues with IE11 on Windows 7 x64?
Did another reboot make any difference?
About 22 hours ago, I installed August 14, Monthly Rollup KB4343900, Security and Quality Rollup updates for .NET Framework KB4345590, and MSRT KB890830, and in a day's work, I have seen no issues with IE11, nor any other issues.

 

I don't regularly use it, but after trying today it seems that problem has been resolved on my system. Will try few more times in next days and report back if it reappears.

 

It seems that the problem has been resolved on my system too, just like Minimalist posted.
I had done lots of reboots; it was initially still there. But later on it seems to have been resolved.
In the meanwhile also the Office 2010 and .Net Framework August updates installed.
It looks like the issue has settled down.

Sorry for late reply!

 

Great. Thank you very much, Minimalist and FanJ.

That's fine. No need to be sorry, at all.
I know you had to find the time for updates and to reply. And also, sometimes it is better to reply later, so you can be more sure about things.
Thanks very much, once again!

 

Today I encountered the problem again. To me it seems that it could be a combination of August update + Eset + specific website combination. For a few days I was using Kaspersky and didn't get this error. Yesterday I reinstalled Eset and an error reappeared. Refresh solves the problem. It's not a big deal to me, since I don't use IE to much.

 

The minor issue of sometimes IE11 not opening a webpage on first try, needing a refresh to open, I see that every couple of days or even most days, since a long time, not related to the August updates. As it is a very minor issue, I never worried about it. I supposed it was related to an earlier IE/Windows update, or a HMPA update, a G Data IS update, an ABP for IE update, or something else.
I never noticed the IE11 refresh switches x64 to x86 version of IE as you reported. How do you see that? In Windows Task Manager, Processes tab, I see both iexplore.exe and iexplore.exe *32, as always.

 

I noticed it when Eset firewall prompted me to allow network connection for IE after I already created rule to allow it. After some tests I noticed that originally IE is launched from c:\Program Files\Internet Explorer\, after an error and refresh it is run from c:\Program Files (x86)\Internet Explorer\. It seems that IE tries to open webpage with x86 version if opening it with x64 fails.

 

Thanks very much, very informative.
I never did such testing.

 

@Minimalist and @Stupendous Man

I've started a separate thread about IE11.
Please see https://www.wilderssecurity.com/thr...then-a-blank-page-for-a-second-or-two.407344/
Thanks to both of you!

 

No problem installing KB4100347 (Intel microcode updates) on my three Win10 x64 1803 machines.