The code commonly typed as 0x80004oo5 contains the letter “o”; the hexadecimal form is usually 0x80004005, with zeroes. In IIS, that HRESULT is a symptom rather than a diagnosis. It can accompany an ASP.NET Core process-start failure, an invalid web.config, missing deployment files, a runtime or architecture mismatch, unreadable permissions, or a site and application pool that is not running. Capture the complete HTTP status and substatus first, then use the matching IIS, HTTPERR, application, and Failed Request Tracing evidence before changing settings.
What the IIS 0x80004005 error means
0x80004005 is a generic “unspecified error” HRESULT. IIS may display it alongside an HTTP error page, but the code alone does not identify which component failed. The same value can appear at different layers: HTTP.sys may reject a request before IIS receives it; IIS may fail while loading configuration or selecting a handler; or an application process may start and immediately exit.
As an Amazon Associate I earn from qualifying purchases.
The surrounding information is therefore more valuable than the hexadecimal value. A page that says “HTTP Error 502.5 – ANCM Out-Of-Process Startup Failure,” for example, points toward ASP.NET Core process startup. A 500 response with a configuration error points toward IIS or application configuration instead. Record the status, substatus, HRESULT, message text, timestamp, URL, site, application-pool name, IIS version, and application technology before attempting a fix.
Preserve the exact failure before changing anything
Keep a copy of the complete browser error page or monitoring alert. Do not rely on a cropped screenshot that omits the status line or detailed error text. The following details narrow the search immediately:
#1 Best Overall
- 3.5 Inch Hot Plug Hard Drive PowerEdge T340 Tower Server Chassis
- Microsoft Windows Server 2019 Standard Operating System
- Processors: Intel Xeon E-2124 Quad-Core 3.3GHz 8MB CPU, Up To 4.3GHz Turbo
- Memory: 32GB (2 x 16GB) DDR4 PC4-21300 2666MHz Unbuffered Memory
- Hard Drive: 8TB (4 x 2TB) 7.2K RPM 6Gb/s SATA 3.5 Inch HDDs in RAID
- HTTP status and substatus: Record both values, such as the numbers shown in the IIS error page or log fields.
- HRESULT and wording: Copy
0x80004005and every sentence around it. - Time and URL: Use the server’s local time zone and include the exact path and request method if known.
- Site and application pool: Note which IIS site, application, virtual directory, and pool handled the request.
- Application type: Identify classic ASP.NET, ASP.NET Core, PHP, or another IIS handler.
- Server details: Record the IIS version, Windows Server edition, installed .NET runtimes, and whether the server is 32-bit or 64-bit.
If the error began after a deployment, configuration edit, runtime update, certificate change, permission change, or application-pool recycle, record that event. A rollback may be safer than repeated edits while you collect evidence.
Read IIS and HTTPERR logs
Find the IIS entry and its status fields
IIS normally stores W3C logs below C:inetpublogsLogFiles, unless an administrator changed the directory. In the folder for the affected site, open the file covering the failure time and locate the request by timestamp and URL. Read the sc-status and sc-substatus fields together. Also note sc-win32-status when present; it can provide an operating-system error associated with the request.
Do not assume that the newest log file contains the event. Log rollover, a custom path, or a different site identifier can place the entry elsewhere. Confirm the site’s logging directory in IIS Manager and compare the server time with the timestamp in the request.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check HTTPERR when IIS has no matching request
HTTP.sys can reject a request before it reaches a worker process. Those failures may not appear in the normal IIS log. Inspect C:WindowsSystem32LogFilesHTTPERR and find the file covering the same time. Its s-reason field describes why HTTP.sys rejected or terminated the request.
A missing IIS entry combined with an HTTPERR entry changes the troubleshooting path: investigate HTTP.sys, bindings, connection limits, request-queue conditions, or another front-end component rather than editing application code first. If neither log contains the request, verify that you are checking the correct server, site, time zone, and logging configuration.
Determine which IIS application stack is failing
Use the deployment files and IIS configuration to classify the application. An ASP.NET Core application commonly has a web.config entry containing an <aspNetCore> element. A classic ASP.NET application usually uses the ASP.NET .NET Framework modules and handlers without that element. PHP and other frameworks have their own handler mappings and process settings.
This distinction matters because an ASP.NET Core process-start problem is fixed differently from a classic IIS configuration error. Do not copy an ASP.NET Core hosting setting into a classic application, or remove a configuration section merely because it is unfamiliar.
Recommended Free Tools
ASP.NET Core on IIS: verify process startup
Check processPath and arguments
Open the deployed web.config and inspect the <aspNetCore> element. For a framework-dependent deployment, processPath normally identifies the installed dotnet host, while arguments points to the application DLL. For a self-contained deployment, processPath normally points to the application executable and the arguments differ. Use the values generated for the deployment type; do not mix a framework-dependent path with a self-contained layout.
Rank #2
- Windows server license is not included
Check spelling, capitalization where the file system is case-sensitive through a mounted or redirected path, quotation marks around paths containing spaces, and relative paths. A path that worked on a development machine can fail on the server when the published output is in a different directory.
Confirm every published file exists
In IIS Manager, open the site or application and select Basic Settings to see the physical path. Compare that directory with the deployment package. The DLL or executable named by processPath and arguments must exist there, along with dependent files produced by publishing.
Look for incomplete copies, a deployment that left an older web.config, files excluded by a packaging rule, and a path that points to the project folder instead of the published output. If you replace files while the application is running, stop or recycle the application pool according to your deployment procedure so that the worker process does not retain a mixture of old and new assemblies.
Verify the runtime and IIS Hosting Bundle
Install the .NET runtime required by the application and the IIS Hosting Bundle appropriate for that runtime on the server. A framework-dependent application cannot start when its required runtime is absent. Check the installed runtimes from a command prompt and compare them with the application’s target framework and deployment documentation.
The Hosting Bundle installs the ASP.NET Core Module used by IIS. If the runtime is present but the module is missing or damaged, IIS may fail to launch the application even though the DLLs are present. After installing or repairing the bundle, restart IIS services during a maintenance window and reproduce the request.
Separate application failure from IIS integration failure
Run the published application directly on the server from a command prompt, using the same account or an account with equivalent access where practical. For a framework-dependent application, the command commonly resembles dotnet YourApplication.dll; a self-contained deployment normally runs its executable. Use the actual filename from the publish directory.
Watch for missing runtime messages, missing assemblies, invalid configuration, port-binding errors, or an exception during startup. If the application fails directly, fix that application or deployment problem before changing IIS. If it runs directly but fails only through IIS, focus on the web.config, ASP.NET Core Module settings, application-pool identity, hosting bundle, and IIS integration.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Check architecture compatibility
Compare the application’s target runtime identifier and architecture with the server’s installed runtime and the application-pool setting. A 32-bit application may require Enable 32-Bit Applications in the pool’s Advanced Settings; a 64-bit-only dependency may require the opposite. Change this setting only when the application’s published architecture and dependencies support it, then recycle the pool and test again.
Rank #3
- MODEL P74439-005: Compact and affordable HPE ProLiant MicroServer Gen11 powered by Intel Pentium Gold G7400 3.7GHz processor, ideal for file sharing, NAS, and basic business workloads
- READY OUT OF THE BOX: Includes 16GB DDR5 UDIMM memory (expandable to 128GB), one 1TB SATA 6G Business Critical HDD, embedded Intel VROC SATA, dedicated iLO-M.2 port kit, 180w external power adapter and 1/1/1 warranty for dependable plug-and-play server operation
- WHISPER-QUIET & SPACE-SAVING: Ultra-compact mini tower design fits easily in small office spaces; supports wall, flat, or vertical placement for deployment flexibility
- INTEGRATED REMOTE MANAGEMENT: Comes with HPE iLO 6 and embedded TPM 2.0 for secure, license-free remote server administration through shared port access
- EXPANDABLE DESIGN: Two PCIe slots (including PCIe 5.0) and four LFF-NHP drive bays provide robust options for storage and component scalability. Features new MR408i-p controller support for enhanced storage performance
Architecture mismatches can look like generic startup failures because the worker process exits before IIS can return a more specific application message. Check native dependencies as well as the .NET runtime when the managed files appear correct.
Enable ASP.NET Core diagnostics temporarily
ASP.NET Core Module stdout or debug logging can expose the startup exception that the browser hides. Enable it only for a controlled reproduction, choose a directory that the application-pool identity can write to, and monitor disk usage. Reproduce the error, read the generated log, and disable verbose logging afterward. Leaving high-volume startup logging enabled on a production site can consume disk space and disclose implementation details.
Also open Event Viewer > Windows Logs > Application and filter around the failure time. Look for entries from the application, the .NET runtime, IIS, or the ASP.NET Core Module. Match the timestamp and process name with the IIS request rather than treating an unrelated warning as the cause.
Classic IIS and ASP.NET: repair configuration and application state
Validate web.config and other configuration files
A malformed, unreadable, or unsupported configuration section can produce an IIS 500 response with a generic HRESULT. Open the affected web.config and check XML structure, closing tags, quotation marks, duplicate sections, and recently changed values. Confirm that each section is valid for the installed IIS features and .NET version.
Check parent configuration files as well. IIS can inherit settings from the server, site, or application level, so a valid-looking local file may still conflict with an inherited section. If the problem started immediately after an edit, restore the last known-good version and test before making additional changes.
Check file and directory permissions
Confirm that the application-pool identity can read the site’s physical path and execute the files required by the application. In Windows Explorer, inspect the folder’s Properties > Security entries and identify the identity assigned to the pool. Grant only the minimum access required; do not make the entire web root writable as a troubleshooting shortcut.
Permissions must also cover parent directories, uploaded configuration files, native dependencies, and any external folders the application reads at startup. If the site is on a network share, check share permissions in addition to NTFS permissions and verify that the identity is recognized by the remote server.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Make sure the site and application pool are running
In IIS Manager, check the site’s state and the application pool’s state. Start a stopped site or pool, then inspect the pool’s rapid-fail protection and recycling settings if it stops again. A pool that repeatedly crashes usually indicates an application exception, missing dependency, identity problem, or incompatible bitness rather than a need to disable protection.
Rank #4
- This Certified Refurbished product is tested and certified to look and work like new. The refurbishing process includes functionality testing, basic cleaning, inspection, and repackaging. The product ships with all relevant accessories, a minimum 90-day warranty, and may arrive in a generic box. Only select sellers who maintain a high-performance bar may offer Certified Refurbished products on Amazon.com.
- Dell Optiplex 3050 SFF Desktop computer PC, Intel Quad Core i5-6500 up to 3.6GHz, 16GB DDR4, 256GB SSD
- Includes: USB Keyboard & Mouse, USB WiFi adapter, Microsoft office 30 days free trail.
- Port: Front: USB 3.0(2), USB 2.0(2); Rear: DP, HDMI, USB 3.0(2), USB 2.0(2), RJ-45.
- Support 4K (3840x2160) Dual display, makes it easy to connect two monitors at the same time, and you can expand working Windows, mirror content, or expand a single window across multiple monitors.
Verify the site binding—protocol, IP address, host name, and port—matches the URL you are testing. A request sent to a different binding can reach another site and produce misleading logs. If a reverse proxy or load balancer is involved, test the server locally as well as through the public endpoint to identify which layer returns the error.
Review application and IIS events
Use Event Viewer > Windows Logs > Application and System around the recorded timestamp. Classic ASP.NET compilation errors, unhandled startup exceptions, module-load failures, and pool termination events can appear there even when the browser shows only a generic page. Compare the event’s process, site, and application path with the failing request.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Increase error detail without exposing the server
When the status code does not identify the failing module, open IIS Manager, select the affected site, open Error Pages, choose Edit Feature Settings, and temporarily enable detailed errors for diagnosis. Prefer local detailed errors so that sensitive paths, configuration values, and stack information are not returned to remote visitors.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Reproduce the failure from the server itself or through an approved administration connection, record the useful detail, and restore the previous setting immediately. Detailed errors are diagnostic output, not a production security control. Leaving them enabled can reveal file paths, module names, connection details, or exception data to unauthorised users.
Use Failed Request Tracing when logs are inconclusive
Failed Request Tracing (FREB) records the IIS modules, handlers, and configuration stages involved in a failed request. Install the IIS Tracing role service if it is not already present. In IIS Manager, select the site, open Failed Request Tracing Rules, add a rule for the observed status code, and reproduce the failure.
Open the resulting XML trace and follow the event sequence. Look for the module or handler that sets the status, a configuration section marked as invalid, an authentication or authorization rejection, a queue or process failure, or a transition to the application process. Remove or narrow the rule after collecting evidence so that tracing does not generate unnecessary files.
Choose the next fix from the evidence
| Evidence | Most likely layer | Next action |
|---|---|---|
| No IIS log entry; matching HTTPERR record | HTTP.sys or an earlier HTTP path | Read s-reason, verify bindings and request conditions, and investigate the HTTP.sys cause before editing the application. |
502.5-style process-start message with 0x80004005 |
ASP.NET Core Module or application startup | Check processPath, arguments, published files, runtime, Hosting Bundle, architecture, and direct command-line startup. |
| 500 response naming a configuration section | IIS or inherited configuration | Validate web.config, parent configuration, installed IIS features, and file readability; revert the latest edit if appropriate. |
| Pool stops or worker process exits | Application, dependency, identity, or bitness | Read Application Event Log, verify permissions and runtime dependencies, then test with the correct pool architecture. |
| FREB identifies one module or handler | Specific IIS pipeline component | Correct that module’s configuration or mapping instead of changing unrelated application settings. |
Retest and document the repair
- Apply one focused change at a time, such as restoring a known-good configuration file, correcting a path, installing the required runtime, or fixing a permission.
- Recycle only the affected application pool unless broader IIS or operating-system changes require a planned service restart.
- Request the exact failing URL locally and through the normal front end, recording the new status and timestamp.
- Confirm that a fresh IIS log entry shows the expected status and that no corresponding HTTPERR or application error remains.
- Disable temporary detailed errors, stdout/debug logging, and FREB rules after collecting the evidence.
- Record the root cause, changed file or setting, runtime and Hosting Bundle versions, and rollback procedure for the next deployment.
If the error returns only after deployment, compare the published directory, web.config, runtime inventory, application-pool identity, and architecture with the last working release. If it returns after an idle period or recycle, inspect startup code, environment variables, secrets, and external services that the application accesses during initialization.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can address some common Windows issues, clean temporary and cache files, review certain settings and vulnerabilities, and provide tools such as real-time boost, file shredding, and crash logs. It complements antivirus software rather than replacing it; results vary and no tool repairs every crash. It runs on Windows 11, 10, 8, and 7, with a category-based free trial of at least two days before a paid subscription.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
