My excel keeps crashing on aws windows server 2016

My excel keeps crashing on aws windows server 2016 update#

So, remember вЂ“ when using Windows Server 2016, set your system proxy settings by using the netsh command and everything will work just fine!

My excel keeps crashing on aws windows server 2016 update#

You can do further reading & testing, but the thing that helped in our case was setting the system (winhttp) proxy with netsh command, so that it actually imports IE proxy settings.Д«asically, you need to run netsh winhttp import proxy source=ie (after youвЂ™ve set the right proxy settings through IE dialog, of course) or set your system proxy by using the netsh winhttp set proxy :8080 command.ДЄfter that, Windows Update starts working again! So, youвЂ™re (naturally) configuring new machines accordingly. Still a bit confused, you have a great idea to check system proxy settings by running netsh winhttp show proxy вЂ“ on older machines youвЂ™ll probably see something like this (which is probably OK, because youвЂ™ve just seen the Proxy Settings in IE, which are set to correct values): Start cataloging your apps and contacting vendors now to understand where they are headed. Start thinking about how your app publishing environment will look when moving to a Desktop OS.

ItвЂ™s not networking, itвЂ™s not proxy settingsвЂ¦ what could it be? Most all my customers have VDI on Windows 10 and published apps on Server 2016. You are checking the configuration of older machines by opening up Internet Explorer and double-checking proxy settingsвЂ¦ and then you make sure that your new machines are having the same configuration вЂ“ they have. You will soon realize that you have some вЂњoldвЂќ Windows Server 2012 R2 (or even Windows 10) machines, which are updating just fineвЂ¦ even through the вЂњfancy proxy thingвЂќ. So, the next logical next step is to blame вЂњthose networking guysвЂќ, because updating your machine works fine, when not behind their вЂњfancy proxy thingвЂќ. Of course, you have some sort of proxy on your network, and you start troubleshooting this issue by testing on a proxy-free networkвЂ¦ and without proxy, Windows Update works just as it should! It just gets stuck on Checking for updates/Downloading updatesвЂ¦ for days. The dumbest thingвЂ¦ you are installing your brand new Windows Server 2016 machines and then you realize that Windows Update doesnвЂ™t work.