WinHTTP Proxy Service Stopping on Server 2019

Copper Contributor

I am having an issue with a few of our Windows server 2019 VMs.

Every week weeks one of the boxes would suddenly be unable to send HTTP requests.

Upon further investigations into the Event Viewer, we found this entry around the start of the issue.


The WinHTTP Web Proxy Auto-Discovery Service service terminated with the following service-specific error:
The endpoint mapper database entry could not be created.


Has anyone ever had this issue or knows a fix? 

We need to restart the VM for it to rectify as the WinHTTP Service refuses to start using the services control panel. The services on those box support 24/7 products and we don't have anyone on call to restart the box at a moments notice.


9 Replies


Scan didn't find any integrity violations

Dont know if you have a fixed proxy, but here is reseting the proxy

Or if you are not using it or is affecting symantec, just disable on regedit.
Hope it works

Hi @DylanDD13 


I am recently getting the same issue on my computer. After that, I tried to run the command - netsh winhttp reset proxy to reset the proxy. (Refer to guide here)


It will reset your proxies and caches and your problem will most probably be fixed. However, If your problem is still not fixed then you can try this method.


Open your browser and go to its proxy section. This step might vary from browser to browser, In most of cases, it is Google Chrome Browser. 


Enter this URL on Google Chrome - chrome://net-internals/#proxy


After that Reset and select "use system proxies" and it will start working again. 


Hopefully, this will give you an answer to your problem. Thanks!!











There might be windows update error that might be causing issue you can try updating the system.



Hello DylanDD13,


WinHTTP Web Proxy Auto-Discovery is a Win32 service. It provides support for auto-discovering a proxy configuration by implementing the Web Proxy Auto-Discovery (WPAD) protocol.


If the WinHTTP Proxy Service Stops and throws an error, "The endpoint mapper database entry could not be created." then you can follow the steps below to troubleshoot the issue.


Boot the system in safe mode with networking:


Booting your computer in Safe Mode with Networking forces your computer to load with only the essential drivers and services.


  • Firstly, press the Windows key on the keyboard and click Power.
  • Next, while holding the SHIFT key on the keyboard, click Restart.
  • Now, Windows will reboot and prompt with a few different options.
  • Then, select Troubleshoot and choose Advanced Options.
  • Now, select Startup Settings and click Restart.
  • After rebooting, Windows will prompt with several other startup options.
  • Lastly, press the number key on your keyboard to enter Safe Mode with Networking.


Thus, you can launch programs, browsers and download files from the desktop to fix any issues you might have. You can simply restart the system from safe mode to return to normal mode.


Perform a clean boot in the Windows server:


A "clean boot" starts Windows with only essential drivers and programs to diagnose problems.


  • Firstly, select Search, type msconfig, and then select System Configuration.
  • Next, on the Services tab of System Configuration, select Hide all Microsoft services, and then select Disable all. Select Apply.
  • Now, In the Startup tab of System Configuration, select Open Task Manager.
  • Then, on the Startup tab in Task Manager, for each Enabled startup item, select the item and then select Disable.
  • Nextly, close the Task Manager.
  • Lastly, select Ok to restart the server on the Startup tab of System Configuration.

Note: After restarting the server, you'll have a clean boot environment. You must restore the system with changes made after completing your troubleshooting.


Check and Repair System Files:


You will have to scan all protected system files to review for any corrupted files on your system.

  • Firstly, click on Start, type cmd, and a command prompt will appear
  • Now, right-click on Command Prompt to open with Admin rights.
  • Then, type the below command and hit Enter to proceed:

SFC /scannow

Note: You will have to wait until the process complete

If you get an error message containing corrupted files, then remove the corrupted files.

  • Lastly, restart the Windows server.


I hope the above ways help you to troubleshoot the issue and that WinHTTP Proxy Service starts without facing any errors.







Yes i have the same issue. We tried completely re-installing the vm from scratch. Doesn't help. After a few weeks the Win HTTP proxy service breaks down.


This ONLY happens on this one VM.


It's only running IIS with two websites. One of the websites uses Microsoft Identity provider for azure SSO and this stops working. Everything else for both websites work fine.


NONE of the "fixes" written in this topic works. The worst advise is the one given about running a "safe boot".. COME on.. Microsoft just fix this **bleep** issue which has been present since the beginning of time and stops CRUCIAL web services from working!!!!


One might almost come to believe they made this problem on purpose to get people to use Azure hosting instead.



You're facing an issue with the WinHTTP Proxy Service on your Windows Server  2019 VMs. The service stops, causing HTTP request failures. The error message suggests a problem with the endpoint mapper database entry. Restarting the VM temporarily resolves the issue, but it's not ideal for 24/7 products. Ensure VMs are updated, try alternative methods to restart the service, and consider contacting Microsoft support for assistance. Implement monitoring to respond promptly. Resolving this issue requires further investigation and contacting support.


This is a known error that Microsoft does not intend to fix. It only effects 2019.

If it doesn't contact a website at least every 27 minutes, the WinHTTP Web Proxy Auto-Discovery Service will stop. Each time it starts up again it creates a new endpoint, which causes it to eventually run out of endpoints, then flood the event log with "The endpoint mapper database entry could not be created" messages.

To prevent it from happening we created a scheduled task that runs every 15 minutes and executes this command, so that the service doesn't ever stop.

"Powershell.exe -NoProfile -NonInteractive -Command "try { Invoke-WebRequest 'http://<Insert_website_to_contact_here>' -ErrorAction Stop } catch { Write-EventLog -LogName Application -Source WSH -EventId 0 -EntryType Information -Message 'The keep-alive task for WinHTTP Web Proxy Auto-Discovery Service failed to contact a website.' }"