If you use Google servers for your email, you may start getting a JavaScript error. This is cause by Google no longer supporting “less secure apps”. I have run across this several times with clients who use Microsoft Outlook. Each instance they also has IMAP, however this may apply to POP configurations too.
While I disagree that Outlook is a “less secure app”, we have to go with what Google says, not what we think.
Regardless if you are getting this pop up when trying to access your mail, the patch is easy.
First close Outlook, you may have to use “Task Manager” to stop it.
DANGER WILL ROBINSON – You will be editing your registry, so be aware.
Let’s backup your registry. We will click the Windows ‘start’ button in the lower left corner of your screen (middle left of Windows 11) and type in “regedit”.
Once the registry editor opens go to the upper left corner and click on “File” and then “Export”. Windows will open a new window. I strongly suggest you navigate to your “C:” drive. By exporting it there, if an issue occurs recovery is easier to access. So in the “Save in” area (top center of the window) select the drop down and select “Windows C:”
I would give it the name “regbu” for registry backup. This may take a minute or two to complete. When the hour glass is gone, it is done.
Now we need to navigate the left column of the registry to the following by clicking on the arrows.
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\ FEATURE_BROWSER_EMULATION
Find the REG_DWORD OUTLOOK.EXE and double-click to edit. Select “Decimal” (by default it opens to hexadecimal) and change the value to “11001”.
In every case where we had the JavaScript error, the decimal number was ‘10001’ as in the example below.
Once you have changed the decimal value to 11001, select “ok” and then close the registry editor.
Now you can open Outlook and all should work.
Until we meet again, have a virus free week.
Hi, can you change the notes above to match the picture of what to change the Value data?
Above this picture is says change to 11001 but in the picture it says 10001 which is the correct one.
I spent an hour trying to figure out why this fix, using 11001 did not work only to realize, due to a friend who pointed it out, that it should have been 10001.
I was super happy it fixed my issue but wow I should have read further down! lol
I seriously wonder how many others did this before realizing their mistake.
Love this fix, it saved hours and hours of searching, which we all do when Microsoft screws around with things and not telling us…
Thank you so much for this!
Wayne