Look out – Here comes IE 11!

For many of us that have been watching the recent pre-releases from Microsoft (Windows 8.1 tomorrow!), IE11 will be a welcome update.  In fact, it will be released as an “Important” update for Windows 7 and up, in order to ensure a large footprint.

However, some companies are barely getting through Windows 7 migrations, or have limited resources available to test their applications against the latest browser, and would like to slow the flow of the river of updates a bit…

So for people/companies that perform automatic updates (or standard deployment of “Important” updates) but *don’t* want IE11 to come down to their workstation, there is a toolkit available to stop the IE11 deployment for Windows 7 or Windows Server 2008 R2 when using Automatic Updates.  


Note that for those of you who have used these toolkits in the past for previous versions, the previous toolkits will not stop automatic deployment of IE11, since each uses a different set of registry keys.

Now get that migration done, so you can go to Windows 8.1!!

2017-07-27T00:01:03+00:00 October 17th, 2013|Uncategorized|

About the Author:

Jeremy is just a regular guy that likes to occasionally tell the world about stuff.

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113