Tag: windows

CURL on Windows

CURL on Windows can be confusing at times

MS Windows has the CURL app installed (since around 2018 at least).

If you run it in powershell, it may behave a little oddly. This is because powershell adds an alias to an internal powershell command called “Invoke-WebRequest”.

You can run curl on the normal commandline and it will use the traditional curl application instead of the his powershell mapped alias.

Or, in powershell you can specify “curl.exe” instead of just plain “curl”, and it will (should?) force powershell to use the curl app instead of the aliased Invoke-WebRequest version.

This page was reviewed by grok here- cURL on Windows

A timeout was reached (30000 milliseconds) while waiting for the….

A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

My new and really fast laptop has been occasionally freezing all input for a long period.. maybe a minute, maybe more.. and then suddenly unfreezes and catches up. I can still move the mouse around, but no clicks and no keyboard input is accepted.

What the heck?

The error above is what I found in the event viewer after it just happened today.

Any solutions out there?

Running Windows 8 64, Dell XPS 15.

A big ol SSD too. Hope that’s not going out…

Update: I’ve noticed this error shows up in searches for a lot of similar errors, such as:

a timeout was reached (30000 milliseconds) while waiting for the windows error reporting service service to connect

a timeout was reached (30000 milliseconds) while waiting for the print spooler service to connect

a timeout was reached (30000 milliseconds) while waiting for the file replication service to connect

a timeout was reached (30000 milliseconds) vmtools

and also while waiting:

for a  transaction response from the VMTools service

for the Symantec Endpoint Protection service to connect

for the SQL Server Reporting Services service to connect

a transaction response from the AudioEndpointBuilder service

a transaction response from the ShellHWDetection service

Ok so the list is too long…