Recommended Free Tools
If Windows shows 0x80070422 while installing .NET Framework 3.5, enable and start the Windows Update service, restart the computer, and try the installation again. The commonly typed 0x800070422 contains an extra zero; Microsoft documents 0x80070422 as ERROR_SERVICE_DISABLED, meaning a required service is disabled or not running.
Check the exact error before changing Windows
Write down the complete hexadecimal code exactly as it appears. Microsoft’s error table identifies 0x80070422, not 0x800070422, as ERROR_SERVICE_DISABLED. The extra zero in the longer version may be a transcription error, but the context still matters: note whether the failure happened in Windows Features, Windows Update, a program installer, or after a restart.
As an Amazon Associate I earn from qualifying purchases.
.NET-related operations can produce several different hexadecimal codes. A message mentioning 0x800F0906, 0x800F081F, 0x800F0907, or 0x800F0922 points toward blocked optional-component content, policy, or a source problem rather than the same service-disabled condition. Do not substitute one code for another when searching for a fix.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What 0x80070422 means
Microsoft classifies this code as ERROR_SERVICE_DISABLED. In the Windows Update context, the update service has stopped, is not running, or has been configured so that Windows cannot start it. Installing or enabling a Windows component such as .NET Framework 3.5 may need Windows Update to download or stage files, so the component operation can fail even though the .NET installer itself is not damaged.
#1 Best Overall
The message often appears in wording similar to “The service cannot be started because it is disabled.” That describes a service state, not proof that Windows is infected and not a guarantee that one command will repair every computer. A disabled service can result from an intentional administrator policy, a previous troubleshooting change, incomplete maintenance, or a damaged update configuration.
Prepare safely
- Sign in with an account that can change Windows services. On a managed work or school computer, policy may prevent you from making the required change.
- Save open work and plan a restart. Windows Update and optional-feature servicing can leave a pending operation until Windows reboots.
- Record the exact .NET version and installation route. .NET Framework 3.5 is an optional Windows component, while other Framework versions may use a separate installer or update package.
- If the error began immediately after a policy or security change, note that timing; it can help an administrator identify why the service was disabled.
Fix 0x80070422 in the recommended order
1. Set Windows Update to Automatic and start it
- Press Win+R to open the Run dialog.
- Enter
services.mscand press Enter. Confirm the elevation prompt if Windows displays one. - In the Services window, locate Windows Update. You can click the list and type the service name to jump to it.
- Open the service’s properties, then find Startup type.
- Set Startup type to Automatic. If the service status is stopped, select Start.
- Select Apply, then OK. Close the Services window.
- Restart Windows and repeat the .NET operation that produced 0x80070422.
Microsoft’s support guidance specifically recommends this sequence. If Startup type is controlled by an organization, or Windows immediately changes it back, do not repeatedly force the setting; ask the device administrator to review the policy.
2. Run the Windows Update troubleshooter
Use the Windows Update troubleshooter available in your edition of Windows. Open Windows Settings, go to the system troubleshooting area, choose the additional or other troubleshooters list, and run Windows Update. The exact grouping of these settings differs between Windows 11 and Windows 10, but the troubleshooter is named Windows Update.
Allow the troubleshooter to apply the changes it reports, restart if requested, and retry the operation. A troubleshooter can identify a stopped service or a common update configuration problem; it does not establish that every component failure has the same cause.
3. Reset Windows Update components when the service is enabled but updates still fail
If Windows Update is set to Automatic and runs, but the installation still returns 0x80070422 or another update error, follow Microsoft’s official Windows Update component-reset procedure for your Windows version. That procedure resets update caches and related services in a controlled sequence. Use Microsoft’s current instructions rather than copying an unverified script, because service names, permissions, and restart requirements can differ by release.
After completing the reset, restart Windows and test Windows Update before attempting .NET Framework again. If the reset changes nothing, record the new error code; a code beginning with 0x800F09 often indicates a separate optional-component source or policy issue.
4. Repair a damaged .NET Framework installation
If applications fail to start, or a newer .NET Framework version cannot install even after Windows Update works, use Microsoft’s .NET Framework Repair Tool. Microsoft recommends this tool when corruption in the Framework installation causes application-start failures or blocks installation of a newer Framework version.
- Obtain the repair tool from Microsoft’s official .NET Framework repair documentation.
- Close programs that use .NET and run the tool with the permissions it requests.
- Read the detected issues and allow the recommended repair to complete.
- Restart Windows when prompted, even if the tool does not make the restart mandatory.
- Retry the application or Framework installation and compare the resulting code with the one you recorded earlier.
The repair tool addresses Framework installation problems; it does not replace the Windows Update service steps. A damaged Framework and a disabled update service can exist on the same computer, so complete the service troubleshooting first when 0x80070422 is the message you see.
Special handling for .NET Framework 3.5
.NET Framework 3.5 is delivered as an optional Windows component. Enabling it may require Windows to obtain component files from Windows Update or from an approved alternate source. Therefore, a successful Windows Update service start is necessary in many cases but may not be sufficient.
Check Windows Update connectivity
Confirm that the computer can reach Windows Update and complete an ordinary update check. If ordinary updates cannot download, resolve that connectivity or update problem before enabling .NET 3.5. A proxy, firewall, disconnected network, or restricted service endpoint can prevent the component payload from arriving.
Check WSUS or organizational policy
On a work or school device, Windows may be configured to use an internal Windows Server Update Services (WSUS) server. An organization can also restrict whether optional-component repair content may be downloaded directly from Microsoft. If the device is WSUS-managed, ask the administrator whether the required .NET 3.5 content is approved and whether policy permits an alternate repair source.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use an approved alternate source when required
Microsoft’s blocked-installation guidance covers cases in which Windows Update cannot supply the .NET 3.5 payload and an alternate repair source is required. Use only installation media or a source supplied and approved for the exact Windows edition and build. A mismatched source can produce another servicing error instead of fixing the first one.
Interpret common 3.5 installation codes
| Code | What it generally signals | What to investigate |
|---|---|---|
| 0x800F0906 | Windows could not download the required feature files. | Windows Update connectivity, proxy or firewall restrictions, and WSUS policy. |
| 0x800F081F | The source files for the feature could not be found. | Whether an approved alternate source or matching installation media is available. |
| 0x800F0907 | Policy prevented Windows from obtaining or using the required source. | Group Policy and WSUS configuration on an organization-managed device. |
| 0x800F0922 | The optional-feature operation could not complete through the servicing path. | Update connectivity, servicing prerequisites, and the source or policy conditions described by Microsoft. |
These codes are not replacements for 0x80070422. First capture the code that appears now; then follow the branch that matches it.
Choose the right troubleshooting path
| Observed symptom | Best first path | Scope | Relative risk |
|---|---|---|---|
| 0x80070422 or “the service cannot be started because it is disabled” | Set Windows Update to Automatic, start it, restart, and retry. | Usually one computer’s service configuration. | Low; it changes one Windows service setting. |
| Windows Update is enabled, but updates repeatedly fail | Run the Windows Update troubleshooter, then follow Microsoft’s component-reset guidance. | Windows Update’s local configuration and caches. | Moderate; follow the official sequence exactly. |
| Applications fail to start or a newer Framework will not install | Run the .NET Framework Repair Tool after update servicing is functional. | The local .NET Framework installation. | Moderate; reboot and retest afterward. |
| .NET 3.5 returns a 0x800F0906, 0x800F081F, 0x800F0907, or 0x800F0922 code | Investigate update connectivity, WSUS policy, and an approved alternate source. | Optional-component servicing, often affected by enterprise policy. | Varies; changing organizational policy requires an administrator. |
Common mistakes and how to recover
Changing the wrong service
Windows has many services with similar names. Change Windows Update, not a similarly named third-party updater. If you altered another service, restore its previous startup setting and restart before testing again.
Starting the service without applying the setting
Selecting Start may run Windows Update temporarily while leaving Startup type disabled. Set Startup type to Automatic, choose Apply, and then confirm that the service remains running after a restart.
Repeating a reset without checking the new code
A component reset is not a universal cure. If the message changes to an 0x800F09xx code, stop repeating the same reset and investigate source, connectivity, or policy conditions instead.
Best Value
Using an unofficial .NET download
Do not replace a missing optional component with an installer from an unknown site. Use Microsoft’s Framework documentation and an approved Windows installation source that matches the device.
Ignoring a managed-device restriction
If Windows reports that settings are managed, the local account may not be allowed to enable the service or obtain optional-feature content. Give the administrator the exact code, the service’s startup state, and whether ordinary Windows Update succeeds.
When the manual steps do not solve the problem
At this point, collect the exact code after the latest attempt, the Windows edition and build, whether Windows Update can install an ordinary update, and whether the device uses WSUS or another management system. Those details distinguish a local service problem from an enterprise policy or source problem.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11If the service will not start even when configured as Automatic, Windows may have deeper servicing damage or a policy that immediately disables it. Use Microsoft’s current Windows Update troubleshooting and component-reset guidance, then contact Microsoft support or your organization’s administrator if the documented steps cannot be completed. Avoid deleting service registry entries or disabling security controls as an experiment; those changes can create additional repair work without addressing the cause.
Quick Recap
As an optional shortcut after trying the manual steps, Outbyte PC Repair can look for common Windows problems such as broken system elements, invalid redirects, shared DLL issues, excess temporary and cache files, and crash-log entries, and it includes settings tweaks and vulnerability checks. It runs on Windows 11, 10, 8, and 7, offers a free trial by category for at least two days before a subscription, complements antivirus software rather than replacing it, and results vary; no tool repairs every crash.
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.
