After Tuesday August 11, 2015, many users began to report receiving Flash Player alerts or warnings when using Internet Explorer 11 (IE11) on Windows 8.1 or Windows 2012R2. These popups warn about action scripts and other flash features.
The good news is that there is nothing to worry about. Your computer was NOT hacked or infected.
What happened was that in the August 2015 Windows updates, Microsoft accidentally updated the embedded flash player in IE11 with the “debugger” version of flash player instead of the normal version.
Microsoft has updated the notes for KB3087916 to reflect this known issue, which Microsoft says should be fixed by August 18th.
I have used Roboform as my password manager solution for what seems like forever. But forever may be coming to an end.
I upgraded my business workstation and laptops over the weekend to Windows 10. Except for a video driver issue and a Bios update, the in-place migration went very smooth. And, for the most part, I’m loving Windows 10.
I was looking forward to really testing out Microsoft Edge, which is the new browser software that Microsoft released along with Windows 10, and it is intended to eventually replace Internet Explorer.
But, according to this Roboform post, Microsoft Edge does not currently support “extensions”, and therefore Roboform will not work with the new browser. According to several websites, support for extensions will not be coming to Microsoft Edge until later this fall. Aarrgghh!!!!
Roboform offers three workarounds …
- Make Internet Explorer 10 your default browser, rather than Microsoft Edge.
Fortunately, Windows 10 comes with both Microsoft Edge and Internet Explorer.
To make IE your default browser, click Start –> Control Panel –> Default Programs –> Set your default programs –> locate Internet Explorer –> click “Set this program as default”
- Use Firefox or Chrome as your default browser
- Or, if you open up a website from within Microsoft Edge, you can click on the “three dotted” icon on the top right, and then select to open that web page using Internet Explorer.
Post revised 4/30/2014
Over this past weekend (April 27, 2014), there have been numerous reports of another zero-day security flaw with Internet Explorer. Some sites have gone so far as to say :”stop using Internet Explorer” completely until this flaw is fixed.
But given that the vulnerability exists in a now deprecated VML vector graphics format, there is an easy workaround solution that is recommended by Microsoft and others — simply unregister the VGX.DLL system file that is associated with this deprecated format.
To unregister VGX.DLL manually
These instructions should work for XP, Vista, Windows 7, and Windows 8 computers. Before starting, you will need to know if you are running a 32-bot or a 64-bit version of Windows.
- Press “WIN“+R keys to display the Run window.
“WIN” = Windows key next to the ALT key. Press the “WIN” key like a Shift key, and then press the letter “R“)
- Type (or copy and paste) the following command into the Window, including the double quotes:
“%SystemRoot%\System32\regsvr32.exe” -u “%CommonProgramFiles%\Microsoft Shared\VGX\vgx.dll”
- Wait for a response window to appear telling you that the command was successful.
- If you are running a 32 bit version of windows, you are done.
- If you are running a 64 bit version of Windows, you need to repeat steps 1-2-3, but using the following command instead:
“%SystemRoot%\System32\regsvr32.exe” -u “%CommonProgramFiles(x86)%\Microsoft Shared\VGX\vgx.dll”
For more information:
This is from the “wish I knew about this sooner…” department.
Microsoft released earlier this year the Internet Explorer 10 Blocker Toolkit for Windows (x86 and x64) and Windows 2008 R2 SP1. This patch does not pertain to networks that are running an update management tool, such as WSUS, that provides the ability to block IE10 from being rolled out.
For all other workstations, you can download and run this tool manually from each workstation. The tool is a .EXE file that contains three files to be extracted.
- Create or identify a temp folder to be used (e.g. c:\temp)
- Download and run the IE10 Blocker Toolkit.
- Click Yes and then select the temp folder from step 1 to extract the three files
- Open up an elevated command prompt, and use the CD command to switch to the temp folder
- Type ie10_blocker.cmd /B and press Enter to set the block for IE10.
- Check that you receive “The operation completed successfully” message, and then close the command prompt window.
As a reminder, IE10 is only pushed out for Windows 7/2008R2 and above. So, there’s no need to run this command script on Windows XP or Vista or Windows Server 2003.
You just upgraded your workstation to Internet Explorer 10. But when you try to remote into your SBS 2008 server, you get a “VBScript: Remote Desktop Connection” error message, like this:
The detail error message reads: The wizard cannot configure Remote Desktop Connection settings. Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer.
The solution is so easy, you probably will miss it. After clicking OK on the error window, click on the Compatibility switch icon at the top of your IE10 window.
Your RWW login screen will refresh. Log back in and try connecting to the remote computer, and it should be working as expected.
N.B. It probably is incorrect to call this a “solution”, as it is more of a “workaround”. It’s not a bug with IE10, it’s that the decision was made that it’s acceptable to have a “workaround” rather than to fix IIS to flag compat mode from the server.