Win7 Monthly Rollup KB 4022719 triggers printing problems in Internet Explorer

Topic

New Reply

EverWilli, posting on the Microsoft Answers forum, describes a problem with the latest Win7 Monthly Rollup, KB 4022719: After installing KB4022719 our
[See the full post at: Win7 Monthly Rollup KB 4022719 triggers printing problems in Internet Explorer]

1 user thanked author for this post.

gkarasik

Reply | Quote

Replies

I have two questions for you. Why are you using Internet Explorer 11?  Woody has been recommending for as long as I remember to use something else.  The second question is why are you applying the changes so quickly and not waiting for Woody to give the Ok on the updates after they have been out for a while.

2 users thanked author for this post.

JDeC, Seff

Reply | Quote

If the person in question did not install this patch you would have not know that the patch has a problem.  So, when you finally decided to install the patch you might have ran into the problem.

Instead of telling the brave soul (by asking rhetorical questions) not to install patches, you should thank the early adopter for finding the issue and reporting it so you can avoid the problem patch.

Thank you, EverWilli whoever you are.

8 users thanked author for this post.

Great Lake Bunyip, Elly, dononline, JDeC, Kobold Curry Chef, ryegrass, Spiff, Alice

Reply | Quote

Woody’s abode is a sanctuary of wisdom on the internet, but not everyone out there knows about it.

All I can say is, I would NOT want to manage hundreds of Windows systems outside of a domain environment. Like that one person who posted saying he managed 300+ computers, some not connected to a domain (not sure how many). Yeah, he’s got a bit of a challenge on his hands.

I’m waiting for friends and family to call me about this. Thankfully I’ve got most of them using browsers other than IE.

Reply | Quote

If you don”t listen to the Doctor (Woody) then don”t blame him if you get sick and have to go in the hospital.

Reply | Quote

This doesn’t just affect those who installed the patch. Those of us who develop software are dealing with supporting those who encounter this issue. The person you are supporting often doesn’t understand what happened or have the permission to rollback/opt out.

Being able to point the users to posts like this is a huge help.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Why install a rollup and not a security only if you cannot wait for the all clear?

Reply | Quote

NOBODY does proper regression testing on browser print functionality.

Why should they? I mean, come ON… The ONLY function of a browser is to render advertising, right? So if that works correctly, then we’re DONE. And besides… The change(s) we’ve made couldn’t POSSIBLY affect printing.

1 user thanked author for this post.

HiFlyer

Reply | Quote

Microsoft’s Update Quality Assurance Team has botched yet another Windows Update. Oops! I forgot that Nadella, when he became CEO, fired the team and made all updates the responsibility of the programmer who wrote the code!

1 user thanked author for this post.

Karlston

Reply | Quote

We are having the same issue with update KB4022715 on Win 10. Same monthly rollup, same symptoms, same fix.

1 user thanked author for this post.

Reply | Quote

Note: This is Win10 v1607

1 user thanked author for this post.

Reply | Quote

I’m curious if the Security Only Quality Update creates this issue as well. I’d guess it probably does, since it’s likely a security issue under the covers that was patched. The folks mentioning this issue appear to be using WUAU to receive the Monthly Quality Rollup rather than manually applying the Security Only Quality Update.

I’m also curious if Edge has this issue as well.

Reply | Quote

You might provide the URLs of some specific pages to test. I installed both KB 4021558 (IE11 Cumulative Security update for June) and KB 4022722 (Windows 7 x64 Security Only update for June). The updated machine runs Windows 7 professional. It drives an old HP 7310 AIO and prints the frames in the page of frame examples at

http://www.echoecho.com/htmlframes08.htm

http://www.echoecho.com/htmlframes08.htm

Regards,
shopper55

2 users thanked author for this post.

MrBrian

Reply | Quote

Seems like everyone is missing the root point here.  This is a absolute classic case of why these single update, all inclusive rollups always have been and still are such a terrible idea.  Here you have a minor,  nay almost trivial, printing issue caused by the rollup that requires the uninstallation the entire rollup package to correct,

This of course re-exposes the user to other severe problems / security issues that were addressed in said rollup for yet another month.  That re-exposure looks like this:
Operating System Distribution:

• Windows 7:  48 vulnerabilities of which 6 are rated critical, and 42 important
• Windows 8.1: 52 vulnerabilities of which 8 are rated critical, and the remaining 44 important
• Windows RT 8.1: 48 vulnerabilities of which 8 are rated critical, and 40 important
• Windows 10 version 1703: 45 vulnerabilities of which 7 are rated critical, and 38 important.

Windows Server products:

• Windows Server 2008:  45 vulnerabilities, of which 6 are rated critical, and 39 important
• Windows Server 2008 R2: 49 vulnerabilities, of which 6 are rated critical, and 43 important
• Windows Server 2012 and 2012 R2: 52 vulnerabilities, of which 8 are rated critical and 44 important
• Windows Server 2016: 57 vulnerabilities of which 7 are rated critical, and 50 important

Other Microsoft Products:

• Internet Explorer 11: 6 vulnerabilities, 3 critical, 3 important
• Microsoft Edge: 17 vulnerabilities, 11 critical,  5 important, 1 moderate, 1 low

Thanks a bunch Satya

Viper

11 users thanked author for this post.

Bill C., Ascaris, grayslady, jelson, GoneToPlaid, samak, Seff, ryegrass, David F, amraybt, PKCano

Reply | Quote

Hmmmmm Very Interesting………………….

For all those folks that still somehow believe the BS about how much more secure Windows Spyware 10 is (it isn’t and never has been) the tale of the tape below shows a very different story:

 

Windows 7:  48 vulnerabilities of which 6 are rated critical, and 42 important
Internet Explorer 11: 6 vulnerabilities, 3 critical, 3 important

Versus

Windows 10 version 1703: 45 vulnerabilities of which 7 are rated critical, and 38 important.
Internet Explorer 11: 6 vulnerabilities, 3 critical, 3 important
Microsoft Edge: 17 vulnerabilities, 11 critical,  5 important, 1 moderate, 1 low

Thanks Again Satya

Viper

6 users thanked author for this post.

David F, Noel Carboni, samak, Kobold Curry Chef, Seff, PKCano

Reply | Quote

Both of your comments taken together reveal just how Microsoft have totally lost the plot (other than in respect of their marketing ability to seduce millions of innocent users to upgrade their OS purely because it was both the shiny new toy and free)!

1 user thanked author for this post.

grayslady

Reply | Quote

I hope there will soon be an out-of-band fix, either a rollback or a repair of just the cause of this particular problem. And, ideally, not requiring a restart.

GaryK

GaryK

Reply | Quote

I did the roll up.  I use Firefox 54.  After the roll up I printed and had no problem.  Win7 Home premium X64.  Group A.

Reply | Quote

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors.  After installling you get a “Item Not Found” popup when trying to rename folders which you can then click through and complete the rename clicking the “Try Again” button.

Note this has happened so many times before with updates it can be classed as a “Lather, Rinse, Repeat” screwup.  It’s probably just a matter of restoring the correct default Folder Descriptions in the registry but I haven’t tried that yet.

 

UPDATE * UPDATE * UPDATE

As I expected restoring the correct default Folder Descriptions in the Registry fixed the file rename issue

Viper

 

Reply | Quote

ViperJohn wrote:

After installling you get a “Item Not Found” popup when trying to rename folders which you can then click through and complete the rename clicking the “Try Again” button.

Not seeing it on my test systems here when trying to rename folders either locally or on a server. Can you be more specific on how to reproduce it?

-Noel

Reply | Quote

same here Noel. I’m not experiencing the folder problems ViperJohn is getting with KB4022719 on my Win7 SP1 computers (and I have manually downloaded & installed the standalone version of KB4022719 from MS Update Catalog – I don’t let Windows Update download & install KB4022719; I do it myself)

Yeah it would be better if ViperJohn would post the steps to reproduce the problem because I’m not getting it at all.

Reply | Quote

ViperJohn wrote:

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors. After installling you get a “Item Not Found” popup when trying to rename folders which you can then click through and complete the rename clicking the “Try Again” button. Note this has happened so many times before with updates it can be classed as a “Lather, Rinse, Repeat” screwup. It’s probably just a matter of restoring the correct default Folder Descriptions in the registry but I haven’t tried that yet. Viper

Just to help narrow this down: I’m not seeing it on any of my Win7/Ent/32bit/SP1 machines.

GaryK

Reply | Quote

gkarasik wrote:

ViperJohn wrote:

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors. After installling you get a “Item Not Found” popup when trying to rename folders which you can then click through and complete the rename clicking the “Try Again” button. Note this has happened so many times before with updates it can be classed as a “Lather, Rinse, Repeat” screwup. It’s probably just a matter of restoring the correct default Folder Descriptions in the registry but I haven’t tried that yet. Viper

Just to help narrow this down: I’m not seeing it on any of my Win7/Ent/32bit/SP1 machines.

I got hit with it on four machines, all fully updated (Security Only not Rollups) Win 7 SP1 as follows:

1 of x64 Home Premium

2 of x86 Pro

1 of x64 Pro

All corrected after restoring the correct default Folder Descriptions in the Registry.  I have seen this happen so much / so ofter (100’s of times literally) that I have the default registry folder descriptions, in both x86 and x64 flavors, already prepared in “Folder Rename Fix.reg” files.  I just merge them to correct the issue and be on my merry way with just a right click and a confirm.

Viper

Reply | Quote

ViperJohn wrote:

I got hit with it on four machines, all fully updated (Security Only not Rollups) Win 7 SP1 as follows: 1 of x64 Home Premium 2 of x86 Pro 1 of x64 Pro All corrected after restoring the correct default Folder Descriptions in the Registry. I have seen this happen so much / so ofter (100’s of times literally) that I have the default registry folder descriptions, in both x86 and x64 flavors, already prepared in “Folder Rename Fix.reg” files. I just merge them to correct the issue and be on my merry way with just a right click and a confirm. Viper

Hi ViperJohn,

I smartly held off on installing June’s Security Only Rollup. I would love to have your reg files. I want to test them to see if your reg files also resolve another longstanding issue which I have on a couple of my Win7 machines in which folder extensions are hidden in third party programs which have low level I/O disk access. It is a long story about this issue which is tied to the windows indexing service and a MS idiot programmer who claimed that nothing after a period in a folder name is valid in folder names, yet dot 3 folder names have been a feature of DOS since DOS 4.1 as I recall, or perhaps even in DOS 3.2?

Best regards,

–GTP

 

Reply | Quote

GoneToPlaid wrote:

ViperJohn wrote:

I got hit with it on four machines, all fully updated (Security Only not Rollups) Win 7 SP1 as follows: 1 of x64 Home Premium 2 of x86 Pro 1 of x64 Pro All corrected after restoring the correct default Folder Descriptions in the Registry. I have seen this happen so much / so ofter (100’s of times literally) that I have the default registry folder descriptions, in both x86 and x64 flavors, already prepared in “Folder Rename Fix.reg” files. I just merge them to correct the issue and be on my merry way with just a right click and a confirm. Viper

Hi ViperJohn, I smartly held off on installing June’s Security Only Rollup. I would love to have your reg files. I want to test them to see if your reg files also resolve another longstanding issue which I have on a couple of my Win7 machines in which folder extensions are hidden in third party programs which have low level I/O disk access. It is a long story about this issue which is tied to the windows indexing service and a MS idiot programmer who claimed that nothing after a period in a folder name is valid in folder names, yet dot 3 folder names have been a feature of DOS since DOS 4.1 as I recall, or perhaps even in DOS 3.2? Best regards, –GTP

Actually I typo’ed the above.  The “1 of x64 Pro” was supposed to say “did not” have a folder rename issue after the update.  It is also only 6 weeks old with a very short, unconvoluted update history as well.  All the other installs are anywhere from 2 to 7 years old.

I have no problem emailing the Reg files to you.  They are just default registry key exports from a fresh x86 and x64 installs before they had the chance to get screwed up along the way.  Just need to know where to send em.

Viper

Reply | Quote

I have no problem emailing the Reg files to you.  They are just default registry key exports from a fresh x86 and x64 installs before they had the chance to get screwed up along the way.  Just need to know where to send em. – Viper

Would you please post these .reg files on this forum? Or at least list the registry location so we may export our current registry settings before applying the June update?

Reply | Quote

Seff wrote:

Both of your comments taken together reveal just how Microsoft have totally lost the plot (other than in respect of their marketing ability to seduce millions of innocent users to upgrade their OS purely because it was both the shiny new toy and free)!

I believe Microsoft has always excelled in the land of Donald Draper…  where “quality” is determined by the marketing. {really sad, isn’t it?}

2 users thanked author for this post.

Cascadian, ch100

Reply | Quote

I appreciate both the point, and the flashback reference. Thanks.

1 user thanked author for this post.

jelson

Reply | Quote

alpha128 wrote:

Would you please post these .reg files on this forum? Or at least list the registry location so we may export our current registry settings before applying the June update?

The Reg files are far to large (20+ pages for x86 and 40+ pages for x64) to post in the forum.  Ideally these registry keys and the data there-in should be exported from new fresh installs so everything is “factory correct”.  The data in the keys can and does get mucked up over time (3 or 4 times by a MS Windows 7 Update over the last 8 years alone).  An error in the data typically  shows up as “Folder Not Found” error on a Folder rename or creation.  Also a folder you know is there can also suddenly go invisible.

To this day I have no idea why some machines are effected and while others are not.  In this go round 3 of my systems came down with folder rename errors after June 2017 update install.  Merging the appropriate Reg file corrected all of them.  My 4th system (x64 Pro) had no problem with the June update at all (It did however need correction after the KB3172605 rollup during initial setup / updating). Go Figure!!!

For x86 Windows installs you want to export:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions]

.

For x64 Windows installs you want to export both:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions]

and

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\FolderDescriptions]

The only difference between x86 and x64 is the inclusion of the Wow6432Node key for x64 installs.  The data in the keys is the same for Home_Premium and Professional Editions.  I believe it is the same for Enterprise edition as well but I have never had an ENT install to check.

Viper

1 user thanked author for this post.

CraigS26

Reply | Quote

Thank you, Viper.  I have exported the two registry keys you listed for my Windows 7 64-bit machine.

Reply | Quote

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors.

I have found another – after installing KB4022722 I found that I couldn’t move i.e. “cut” followed by “paste” files from my Downloads folder to an external HDD. I kept getting strange messages similar to “the specified location does not exist”. Uninstalling the patch didn’t solve matters, and I had to revert to an earlier system image. One post I saw on similar problems suggested using “Folder Fix” – which didn’t!

Any suggestions?

Reply | Quote

Did you try a System Restore to a point before the patch install?

Reply | Quote

Yes, I use imaging software rather than System restore – much more reliable! I then tried installing the full patch, rather than the security only version, and the same thing happens, so I re-imaged once more… I assume it’s probably a registry issue, but I’m not knowledgeable enough to delve into the relevant areas. A further thought – I normally view folders with “Q-Dir”, but I also tried to drag and drop directly from one Explorer folder to another. Doing that is O.K. – but this merely “copies” the source file, and I was then able to delete it. But If I hold down the “Shift” key and try dragging (which should move and then delete the original), I get the same error message. Similarly, highlighting a file, right clicking and choosing “cut”, then trying to “paste” it in another location results in error messages.

I should have said earlier that I’m running 32 bit Win7 Home Premium.

Reply | Quote

I too have KB4022722 installed, but have not been able to duplicate either the file rename problem, or the cut and paste problem from the downloads folder. This was tested on two different computers, one with Windows 7 x64 Pro, and the other with Windows 7 x64 Home Premium installed.

Reply | Quote

anonymous wrote:

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors.

I have found another – after installing KB4022722 I found that I couldn’t move i.e. “cut” followed by “paste” files from my Downloads folder to an external HDD. I kept getting strange messages similar to “the specified location does not exist”. Uninstalling the patch didn’t solve matters, and I had to revert to an earlier system image. One post I saw on similar problems suggested using “Folder Fix” – which didn’t! Any suggestions?

I’m not seeing this or the reported printing problems on my systems.

GaryK

Reply | Quote

anonymous wrote:

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors.

I have found another – after installing KB4022722 I found that I couldn’t move i.e. “cut” followed by “paste” files from my Downloads folder to an external HDD. I kept getting strange messages similar to “the specified location does not exist”. Uninstalling the patch didn’t solve matters, and I had to revert to an earlier system image. One post I saw on similar problems suggested using “Folder Fix” – which didn’t! Any suggestions?

Folder / file move errors are another manifestation of the folder descriptions in the registry getting [wrec]ked.  I to have never had a previous “System Restore Point” correct the problem once they crop up.  That was one of the reasons I dumped System Restore and went to full off-line disk / logical drive image and restore.  There is literally nothing you can’t recover from with a drive image.

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running.  Re-install the June update then merge the Reg file you created and I would bet your “Cut and Paste” move issue is corrected.

Viper

Reply | Quote

Thanks, Viper. When you say

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running

Do you mean this one?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions]

I have exported this branch and it comes to 100KB – does that sound about right? I don’t want to keep re-imaging more than necessary!

Reply | Quote

I owe you guys (particularly ViperJohn) a huge vote of thanks – I re-installed KB4022722 and the file moving problem returned. The actual wording (I took a screenshot this time!) is:

Could not find this item

This is no longer located in E:\My Documents\Downloads. Verify the item’s location and try again.

 

I merged the saved Registry branch, and initially nothing changed. THEN I membered to reboot, and now I can copy/move/delete and also restore from the recycle bin. Rather annoyingly I noticed that “Libraries” had re-appeared – I hate this feature and keep removing it, but every so often an MS Update puts it back. I have a reg file from another forum which makes removing it easy.

I’ll know where to seek help next time!

Dave W

Reply | Quote

For everyone’s info, as of this writing, June 16th 2017, 1900 Pacific Time, (17 June 0300 GMT/UT) MS is owning up to the printing faux pas in the bulletin for IE11 (KB4021558), and says that they’re looking into it and will release further details as they evaluate further. However, they DON’T say a thing about the printing issue on the bulletin for the monthly rollup (KB4022719). The rollup’s bulletin is still dated the 13th of June, so that explains why.

1 user thanked author for this post.

MrBrian

Reply | Quote

woody wrote:

EverWilli, posting on the Microsoft Answers forum, describes a problem with the latest Win7 Monthly Rollup, KB 4022719: After installing KB4022719 our[See the full post at: Win7 Monthly Rollup KB 4022719 triggers printing problems in Internet Explorer]

Woody,

Just a heads-up for others: I tested 4022719 on several sandbox systems, found no problems, and cleared it for installation on production systems. Yesterday I got a call from a CPA who suddenly couldn’t print forms from an IRS.GOV site. Uninstalling 4022719 solved that problem but created another: A pair of the user’s Intuit utilities would no longer run, complaining that they couldn’t find D3DCompiler_47.Dll. I reinstalled 4022719 which solved the D3DCompiler_47.dll problem but brought back the printing problem. I then used system restore to regress the system to before the installation of 4022719. That solved the printing problem but left the user vulnerable to the other problems 4022709 addresses. I will open a security-patch support ticket with MS Monday, but in the interim I’m now looking for patches I can apply manually to mitigate these other vulnerabilities.

People should know that if problems with 4027719 show up, a simple uninstall may not be an out; uninstalling it can have unintended consequences.

GaryK

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

.Net 4.7 was a checked update for Win7 this Patch Tues. There was a problem with a missing D3DCompiler .Dll if it was installed without the Rollup. The .dll was supposed to be included in June Rollup for Win7 but not in the security-only patch. See https://www.askwoody.com/2017/net-framework-4-7-is-now-available-for-win7-sp1/
There were some other cautions also.
Perhaps the KB 4022719 and .NET4.7 installations are tied to the problems?

Edit to add content

Reply | Quote

anonymous wrote:

Thanks, Viper. When you say

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running

Do you mean this one? [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions] I have exported this branch and it comes to 100KB – does that sound about right? I don’t want to keep re-imaging more than necessary!

Until Viper notices your question … I’m W7-64 SP1 and therefore had TWO .reg Files to EXPORT. The one you show is 116 KB and the WOW6432 one is 119 KB. FYI

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

anonymous wrote:

Thanks, Viper. When you say

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running

Do you mean this one? [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions] I have exported this branch and it comes to 100KB – does that sound about right? I don’t want to keep re-imaging more than necessary!

Yes that is correct.  That is the key for a x86 install and it will be 110K+ (about 20 pages printed out).

For an x64 system you need that same key plus the Wow6432Node key as well which another 110K+.

Viper

Reply | Quote

PKCano wrote:

.Net 4.7 was a checked update for Win7 this Patch Tues. There was a problem with a missing D3DCompiler .Dll if it was installed without the Rollup. The .dll was supposed to be included in June Rollup for Win7 but not in the security-only patch. See https://www.askwoody.com/2017/net-framework-4-7-is-now-available-for-win7-sp1/ There were some other cautions also. Perhaps the KB 4022719 and .NET4.7 installations are tied to the problems? Edit to add content

MS really botched the Net Framework 4.7 release from the gitgo.  You could get 4.7 (and I did) about 3 or 4 weeks ago.  The problem is 4.7 has a dependency on a DLL file (D3DCompiler_47.dll)  that  is normally not in a Windows 7 install as noted here:

https://support.microsoft.com/en-us/help/4020302/the-net-framework-4-7-installation-is-blocked-on-windows-7-windows-ser

My understanding is that installing Net Framework 4.7 on a Win7 system from Windows Update  can also be problematic.  The needed D3DCompiler_47.dll may not get installed at all sometimes or worse yet get installed by the June rollup only to be uninstalled if the Rollup is taken out by a System Restore to correct other June update issues which then breaks Net-Fr 4.7.

For Windows 7 users you can get the needed D3DCompiler_47.dll by installing KB4019990 in either x86 or x64 flavors as required.  You can follow that up with KB3186497 which is the offline installer for Net Framework 4.7 if needed.

Voper

1 user thanked author for this post.

ymo1965

Reply | Quote

ViperJohn wrote:

PKCano wrote:

.Net 4.7 was a checked update for Win7 this Patch Tues. There was a problem with a missing D3DCompiler .Dll if it was installed without the Rollup. The .dll was supposed to be included in June Rollup for Win7 but not in the security-only patch. See https://www.askwoody.com/2017/net-framework-4-7-is-now-available-for-win7-sp1/ There were some other cautions also. Perhaps the KB 4022719 and .NET4.7 installations are tied to the problems? Edit to add content

MS really botched the Net Framework 4.7 release from the gitgo. You could get 4.7 (and I did) about 3 or 4 weeks ago. The problem is 4.7 has a dependency on a DLL file (D3DCompiler_47.dll) that is normally not in a Windows 7 install as noted here: https://support.microsoft.com/en-us/help/4020302/the-net-framework-4-7-installation-is-blocked-on-windows-7-windows-ser My understanding is that installing Net Framework 4.7 on a Win7 system from Windows Update can also be problematic. The needed D3DCompiler_47.dll may not get installed at all sometimes or worse yet get installed by the June rollup only to be uninstalled if the Rollup is taken out by a System Restore to correct other June update issues which then breaks Net-Fr 4.7. For Windows 7 users you can get the needed D3DCompiler_47.dll by installing KB4019990 in either x86 or x64 flavors as required. You can follow that up with KB3186497 which is the offline installer for Net Framework 4.7 if needed. Voper

Thanks, but I’m not sure about this. I installed just the rollup, and then I installed NetFramework47 after that. The problem presented when the rollup was removed, and the problem went away when I reinstalled the rollup.

GaryK

Reply | Quote

Workarounds are at https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12349663/.

Reply | Quote

MrBrian wrote:

Workarounds are at https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12349663/.

Yeah and look at the Microsoft response:

Hello,

Thank you for providing your feedback on IE11. We are not accepting feedback on Internet Explorer through this portal any longer (unless security related). We welcome any feedback you have on Microsoft Edge through this website.

If this is blocking enterprise deployment, please follow the CSS escalation process to engage MS support (GES, General Escalation Service) and file a servicing request.

Best Wishes,
The MS Edge Team

The correct response should have been “We will forward this info to the appropriate parties ASAP.”

Viper

Reply | Quote

ViperJohn wrote:

MrBrian wrote:

Workarounds are at https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12349663/.

Yeah and look at the Microsoft response:
Hello, Thank you for providing your feedback on IE11. We are not accepting feedback on Internet Explorer through this portal any longer (unless security related). We welcome any feedback you have on Microsoft Edge through this website. If this is blocking enterprise deployment, please follow the CSS escalation process to engage MS support (GES, General Escalation Service) and file a servicing request. Best Wishes, The MS Edge Team
The correct response should have been “We will forward this info to the appropriate parties ASAP.” Viper

This makes me wonder if there isn’t a serious problem going forward: If this isn’t fixed, will the problem be included in future rollups? And does that mean that no one who has the problem can apply any future security fix?

GaryK

Reply | Quote

woody wrote:

Win7 Monthly Rollup KB 4022719 triggers printing problems in Internet Explorer
Only solution so far is to roll back the security patch.

Known issues in this security update
When you print a specific iframe or frame in a web page, the print output may be blank, or text is printed that resembles the following:
404 – Not Found
(A frame is a part of a web page or browser window that displays content independent of its container. A frame can load content independently.)
This problem has also been observed in both Internet Explorer 11, and in applications that host the IE Web Browser Control.
There is currently no workaround for this issue. However, if you print the entire web page, it will print correctly.
Microsoft is researching this problem and will post more information in this article when the information becomes available.
Cumulative security update for Internet Explorer: June 13, 2017

1 user thanked author for this post.

PKCano

Reply | Quote

The one microSoft links says “Won’t fix” and offers a work-around: use print preview for printing.

The other microSoft link says “We’ll work on this” and “there’s no known work-around”…

Just great.

I’ll do the update, as I always use the preview first. But really…

Reply | Quote

Susan Bradley recently said that the newest Windows updates are all safe to install (for Windows 7 users).  Yet, I hear about the iFrame printing issue after installation of KB4022719.  The bottom line…  should I install the recent Windows 7 updates, or should I wait?  (P.S.  I have no problem with waiting, as I usually do not install anything until Woody AND Susan Bradley both give the go-ahead.)

 

Reply | Quote

The DEFCON number is still 2 – which means WAIT.
I think it is the IE11 update contained in the Monthly Rollup that is the source of the problem.
Hopefully they will fix this in the near future – not wait till next month’s updates.
Wait a while longer – unless you like being a Guinea Pig.

Reply | Quote

Susan is probably right, because the printing issue is so obscure that it does not even deserve attention.
However, if you follow Woody and chances are that you do if you post here, wait for a little longer to have MS-DEFCON raised at 3 as above.

Reply | Quote

ch100 wrote:

Susan is probably right, because the printing issue is so obscure that it does not even deserve attention…

Tell that to gkarasik…

Reply | Quote

Jan K. wrote:

I’ll do the update, as I always use the preview first. But really…

🙂

Reply | Quote

Jan K. wrote:

ch100 wrote:

Susan is probably right, because the printing issue is so obscure that it does not even deserve attention…

Tell that to gkarasik…

Thanks. I wasn’t going to address CH100’s comment because it was so bizarre,  but I guess I’ll have to.

GaryK

1 user thanked author for this post.

Alice

Reply | Quote

ch100 wrote:

Susan is probably right, because the printing issue is so obscure that it does not even deserve attention.

I hope that, as everyone occasionally does, you dashed this off without thinking much about it, because what you’re saying is sort of like saying that West Nile Virus is obscure because, statistically, it infects very few people. If you’re one of the few it infects, it’s significant to you. There’s a line in Joseph Heller’s “Catch 22” (I hope I’m correctly remembering who says what) when Orr complains that the Germans are shooting at him. Yossarian says, “They’re not shooting at you–they’re shooting at everybody.” And Orr says, “Yes, but the bullets are hitting me.” Likewise, the printing bug may bite only a few, but its impact is significant to the user whose business depends on the ability to print IRS forms from the internet.

GaryK

3 users thanked author for this post.

twbartender, Jan K., Alice

Reply | Quote

ViperJohn wrote:

anonymous wrote:

Thanks, Viper. When you say

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running

Do you mean this one? [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions] I have exported this branch and it comes to 100KB – does that sound about right? I don’t want to keep re-imaging more than necessary!

Yes that is correct. That is the key for a x86 install and it will be 110K+ (about 20 pages printed out). For an x64 system you need that same key plus the Wow6432Node key as well which another 110K+. Viper

Oy–So I don’t have a clean machine from which to export Viper’s reg file, and it turns out System Restore didn’t solve the problem after all. The IRS doesn’t allow printing from other than IE, and Print Preview in IE prints only the initial “print from here” page.

S***wed. I did do a lot of sandbox testing, but as it turns out, not enough. I was concerned about exploits in the wild from the CIA/NSA hack, and that pushed me to install the rollup instead of holding off.

I can’t really blame MS. S***w me once, shame on you; s***w me twice, shame on me.

Edit for content

GaryK

Reply | Quote

gkarasik wrote:

ViperJohn wrote:

anonymous wrote:

Thanks, Viper. When you say

Create a Reg file by exporting the registry keys indicated above from a properly working installed image of the flavor of Windows you are running

Do you mean this one? [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions] I have exported this branch and it comes to 100KB – does that sound about right? I don’t want to keep re-imaging more than necessary!

Yes that is correct. That is the key for a x86 install and it will be 110K+ (about 20 pages printed out). For an x64 system you need that same key plus the Wow6432Node key as well which another 110K+. Viper

Oy–So I don’t have a clean machine from which to export Viper’s reg file, and it turns out System Restore didn’t solve the problem after all. The IRS doesn’t allow printing from other than IE, and Print Preview in IE prints only the initial “print from here” page. S***wed. I did do a lot of sandbox testing, but as it turns out, not enough. I was concerned about exploits in the wild from the CIA/NSA hack, and that pushed me to install the rollup instead of holding off. I can’t really blame MS. S***w me once, shame on you; s***w me twice, shame on me. Edit for content

PM me with your email addy and I will email you virgin REG files in a zipped attachment.

Viper

Reply | Quote

ViperJohn wrote:

Okay we got another MAJOR screw up with Security Only Quality Update KB4022722 (and most likely the Rollup too) in both x86 and x64 flavors. After installling you get a “Item Not Found” popup when trying to rename folders which you can then click through and complete the rename clicking the “Try Again” button. Note this has happened so many times before with updates it can be classed as a “Lather, Rinse, Repeat” screwup. It’s probably just a matter of restoring the correct default Folder Descriptions in the registry but I haven’t tried that yet. UPDATE * UPDATE * UPDATE As I expected restoring the correct default Folder Descriptions in the Registry fixed the file rename issue Viper

My employer pushed the June Security only roll-up to my work machine today.  I installed it, and sure enough I got the “Item Not Found” error you describe.  I called the help desk and they made the very non-intuitive suggestion to run a repair on Microsoft Office.  I tried it and it actually solved this problem!

Reply | Quote

anonymous wrote:

I have two questions for you. Why are you using Internet Explorer 11? Woody has been recommending for as long as I remember to use something else. The second question is why are you applying the changes so quickly and not waiting for Woody to give the Ok on the updates after they have been out for a while.

There are business reasons to use IE11. Some vendors require it to the exclusion of other browsers. For instance, the IRS allows only IE for CPAs needing professional-level access to IRS data.

GaryK

Reply | Quote

ch100 wrote:

Jan K. wrote:

I’ll do the update, as I always use the preview first. But really…

🙂

Using Print Preview doesn’t always solve the problem.

GaryK

Reply | Quote

myitforum.com is reporting that the printing issue affects Windows 7 & 10, and that MS is reporting that the issue is marked “won’t fix” by the Edge team, as well as an update to KB4021558 which indicates a fix is underway by the IE team.

So we can probably take it that “Won’t fix” is a response from the Edge team … as a result of not fully understanding the severity of the issue in the corporate space, or it simply being seen as “not our problem” maybe?

Reply | Quote

gkarasik wrote:

ch100 wrote:

Jan K. wrote:

I’ll do the update, as I always use the preview first. But really…

Using Print Preview doesn’t always solve the problem.

No surprise, but I’ve decided to wait for the IE11 team to solve the issue.

See below…

Reply | Quote

Kirsty wrote:

myitforum.com is reporting that the printing issue affects Windows 7 & 10, and that MS is reporting that the issue is marked “won’t fix” by the Edge team, as well as an update to KB4021558 which indicates a fix is underway by the IE team.

So we can probably take it that “Won’t fix” is a response from the Edge team … as a result of not fully understanding the severity of the issue in the corporate space, or it simply being seen as “not our problem” maybe?

When you look at the Edge team link… “Won’t fix”… there was some angry responses. I don’t understand why the Edge team instead didn’t reply something like “we’ve passed the feedback and requests on to the IE 11 team” together with a link to them.

Why so arrogant?

Reply | Quote

Windowsreport has posted an article which reports a host of other serious problems with KB4022719. These problems include

— The update fails to install with various error codes.

— IE prints blank pages.

— Taskbar icons disappear.

— Outlook will no longer index new email messages.

See:

http://windowsreport.com/kb4022719-bugs/

 

1 user thanked author for this post.

MrBrian

Reply | Quote