Windows 10: Wiindows Update 9/12/17 has killed IE

This week's big patch installed unexpectedly fast considering the list of issues it claims to address, but when the PC came back up, IE was dead. The program file is still there but clicking it gives only a brief hourglass (and brief presence in Task Manager), then nothing. Same situation on both my desktop and laptop.

Uninstalling the patch brought it back, but when it reupdated shortly thereafter IE was gone again.

Minor possible clue: After the first patch, Edge was also unreponsive (it would open, but not browse anywhere). The re-update, strangely, brought it back. Still no IE, which I continue to need, for one (daily and work-related) task.

Any ideas? I know MS wants us all to adore Edge but this probably ain't the best way to go about that. *Mad

:)

 

Windows Power Shell eating CPU

Since the update on 9/15/17, windows powershell keeps pegging my CPU. Can I limit or kill it?

 

Microsoft Word Viewer 2003 is crashing

Hi dniheb,

I found the KB3127962 update, under "Update History". It has been downloaded to our computer twice: Once on November, 9, 2016 and once on November 17, 2016 (seems odd). I then looked for both of these under
the "Uninstall Updates" tab. However, I only found the update from November 17, 2016, listed. The one from November 9, 2016 is not showing (seems odd). I uninstalled the one from 11/17/16 and rebooted the computer.

After rebooting, the KB3127962 update which was downloaded on November 17, 2016 is no longer showing in the "Uninstall Updates" list -it appears it has been deleted, but this has not fixed the problem. We
still cannot view our word documents.

I'm not sure if it matters, but a couple of things to reiterate, in case it is helpful:

1.) Again, this KB3127962 update was listed twice under the "Update History", ie downloaded once on 11/9/16 and again on 11/17/16.

2.) Again, only the 11/17/16 update was showing in the "Uninstall Updates" (which I deleted). And, when I rebooted the computer, the 11/17/16 update was no longer showing here, but the word documents still will not open.

3.) After rebooting, both KB3127962 updates are still showing under "Update History" ie, once on November, 9, 2016 and once on November 17, 2016.

Any other suggestions as to why the app suddenly stopped working?

Thanks for your time.

Sincerely,

Sonya Bruyette

 

Both IE and Edge work fine for me. I don't use either one but I opened up 5 web pages on each to check, no issues.

 

This is solved, with the help of user ricar0 on Tom's Hardware. The source of problem -- as far-fetched as it sounds -- is with the layout of tabs in IE. There's some issue with the latest update that paralyzes IE if you have its tabs set to display on a separate row. You can fix this by either uninstalling the update and unchecking Show Tabs on a Separate Row (right-click menu from any tab), then re-updating, or by editing the registry as explained here.

 

Not that far fetched. The release notes for this update specifically state one of the things updated was...

Cumulative Update KB4038788 Windows 10 v1703 Build 15063.608

A similar IE 11 patch was in the update for Windows 7 where it worked as intended, apparently. After the update this popup appeared on opening IE (I'm guessing that was what was intended to happen in Windows 10 too).





Fortunately my Win10 IE was already set to have tabs on the same row, so apart from some puzzlement I had no problems.

Cumulative Update KB4038788 Windows 10 v1703 Build 15063.608

 

Uh, so it deesn't seem bizarre to you that one of two supposedly legitimate options for a program's tab display would prevent said program from even opening?

The fact that a tab change is shown as an update can't possibly justify this bug.

 

It doesn't for me. I can change from one row to two, close IE then open it without a problem. It opens fine regardless of whether I set it to one or two rows.

This is probably because I had is set to one before the update which was luckily the 'safer' option - it seems that those who suffered problems were the ones who had it set for two rows before the update.