Free tools Windows power users keep installed
One-click scans. No signup required.
“0x8007042” is not a complete, uniquely defined Windows error code. Reports using that truncated text describe different failures, including a disabled Windows Update service and a Windows Firewall startup problem. Before changing anything, capture every hexadecimal digit from the dialog, Event Viewer, or command output. The complete code is often 0x80070422 for an update-service problem or 0x8007042c for a firewall problem, but neither mapping is confirmed for every Windows Server installation.
Why 0x8007042 is ambiguous
Windows error codes normally contain eight hexadecimal digits after the 0x prefix. The string in this title has only seven digits, so it may be truncated by a search result, copied incorrectly, or displayed without a final character. Two Microsoft Q&A discussions illustrate why guessing is risky. A post dated March 18, 2020 used the shortened text while troubleshooting Windows Update and described the Windows Update startup type as locked to Disabled. A separate post dated April 14, 2012 used the same shortened text while attempting to start Windows Firewall and directed readers to guidance for 0x8007042c. A current troubleshooting article instead addresses 0x80070422 for Windows Update.
As an Amazon Associate I earn from qualifying purchases.
There is no published Windows Server-specific definition for the exact seven-digit string. Treat the two longer codes as possible interpretations, not as a confirmed decoding. The component that failed is as important as the number itself.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Capture the complete message
- Open the original dialog again and select or copy the entire error text, including all digits after
0x. - If the dialog disappeared, open Event Viewer by pressing
Win+R, enteringeventvwr.msc, and checking Windows Logs and the component-specific logs around the failure time. - Record what you were doing: installing updates, starting the firewall, opening Microsoft Store, or launching another service. Note the Windows edition and whether the machine is a client PC or a Windows Server installation.
- Do not apply an update fix to a firewall failure, or a firewall fix to an update failure, until the symptom and full code agree.
Quick decision table
| What failed | Code that may match the truncated text | First check | Relative risk |
|---|---|---|---|
| Windows Update will not run, or the update service is Disabled | 0x80070422 is the commonly documented related code; the seven-digit text alone does not prove it |
Windows Update, Background Intelligent Transfer Service (BITS), and DCOM Server Process Launcher startup settings | Low when only service settings are inspected or restarted |
| Windows Defender Firewall will not start | 0x8007042c is the related code cited by the older Microsoft Q&A discussion |
Windows Defender Firewall and its dependent networking services | Low for inspection; moderate if service dependencies or policy settings are changed |
| Another operation, such as Microsoft Store or an application launch | Not established from the available evidence | Capture the full code and inspect the failing component’s log | Varies; avoid unrelated resets |
Check services before changing system files
A disabled or non-starting service is the most direct suspected cause in the related Windows Update cases. Service checks require administrator rights but are reversible. They should come before component resets or a repair installation.
#1 Best Overall
Use the Services console
- Press
Win+R, typeservices.msc, and press Enter. Approve the User Account Control prompt. - For an update symptom, locate Windows Update, Background Intelligent Transfer Service, and DCOM Server Process Launcher. Read each service’s Status and Startup type. Do not change a service merely because it is not currently running; some Windows services start on demand.
- If Windows Update is set to Disabled, open its properties, choose Automatic in Startup type, select Apply, and then select Start. If the service refuses to start, write down the exact message.
- Check BITS in the same way. BITS transfers update files in the background and may be required even when Windows Update itself is configured correctly.
- For a firewall symptom, locate Windows Defender Firewall and inspect the networking services shown as dependencies. Keep the default startup configuration unless the full error and the service status indicate a change is needed.
- Restart the computer and retry the operation once. A restart clears a stuck service state without deleting update data.
Use an elevated Command Prompt for update services
If the Services console cannot save the startup type, open Command Prompt (Admin) or Windows Terminal (Admin) and run the following commands one line at a time:
sc config wuauserv start= auto
sc config bits start= auto
sc config DcomLaunch start= auto
net start wuauserv
net start bitsThere must be a space after start=; that spacing is required by the sc command. A message saying that a service is already running is not a failure. DCOM Server Process Launcher is a core service and may be managed by Windows; if its configuration is protected or the command returns an error, record the message rather than forcing a registry edit. On some installations, BITS or Windows Update may start only when needed, so the startup-type result and the final error are more useful than a simple Running/Stopped label.
Repair the Windows component store and system files
When service configuration looks correct but the update operation still fails, damaged system files can prevent services from registering or starting. Windows includes two repair utilities. Run them from an elevated command window and allow each one to finish.
Run System File Checker
- Open Windows Terminal (Admin) or Command Prompt (Admin).
- Enter
sfc /scannowand press Enter. - Wait until verification reaches 100 percent. Do not close the window or power off the machine.
- Read the final message. If Windows repaired files, restart and test Windows Update again. If it found corrupt files but could not repair some of them, continue with DISM.
Run DISM, then run SFC again if needed
- In the same elevated window, run
DISM /Online /Cleanup-Image /RestoreHealth. - Let the operation complete; progress can pause for an extended period while the component store is checked.
- Restart Windows after DISM finishes.
- Run
sfc /scannowa second time if the first scan reported unrepaired files, then retry the operation that produced the error.
SFC and DISM repair Windows components; they do not identify the missing final hexadecimal digit and they do not replace a firewall or update policy decision. If the commands return their own error, save the exact text before attempting another reset.
Reset Windows Update components only when service repair is insufficient
Update caches can become inconsistent after an interrupted download or a failed servicing operation. Resetting them is more disruptive than restarting a service because it removes the local cache metadata that Windows will rebuild. Use this branch only when the complete code and symptom point to Windows Update and the earlier checks did not help.
Before you reset
- Create a restore point if your edition provides System Protection, or ensure that you have a current backup of important data.
- Close Settings, Windows Update, and applications that may be installing software.
- Confirm that you are working in an elevated Command Prompt and that the commands match your Windows version.
- Do not rename folders on a machine that is actively installing updates or servicing a production workload.
Stop services and rename the caches
The documented procedure stops the update services, renames SoftwareDistribution and catroot2, then starts the services again. Renaming preserves the old folders as a fallback while forcing Windows to create fresh ones.
net stop wuauserv
net stop bits
net stop cryptsvc
ren %systemroot%SoftwareDistribution SoftwareDistribution.old
ren %systemroot%System32catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauservIf a stop command reports that the service is not running, continue to the next line. If a rename reports that files are in use, restart the computer, make sure no update process is active, and try again from an elevated prompt. Do not delete the renamed folders immediately; Windows may need time to recreate its working directories and you may want the old cache for diagnosis.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →After the services restart, open Settings > Windows Update on supported client editions, or the equivalent update interface for your Server installation, and retry. If the failure returns with a different complete code, record that code rather than repeating the reset.
Firewall-specific checks for a 0x8007042c interpretation
If the failure occurs when enabling Windows Defender Firewall, stop following the Windows Update branch. In services.msc, inspect Windows Defender Firewall and the networking services listed in its dependency information. A disabled dependency can prevent the firewall service from starting even when the firewall setting itself appears enabled.
- Open
services.mscas an administrator and check the firewall service’s Startup type and Status. - Open the service’s Dependencies tab and inspect each required service. Restore an accidentally disabled dependency to its normal startup configuration rather than selecting arbitrary settings for every networking service.
- Restart Windows, then open Windows Security > Firewall & network protection and check whether the active network profile can be enabled.
- If a domain, group policy, or security baseline controls the firewall, contact the administrator before changing it locally. A policy can reapply a setting after every restart.
The older Microsoft Q&A discussion links this firewall symptom to 0x8007042c; it does not establish that every appearance of 0x8007042 is a firewall failure.
Use a repair upgrade as a later recovery option
When services, SFC, DISM, and (for update symptoms) the cache reset all fail, an in-place repair upgrade can replace damaged Windows components while keeping personal files and installed applications. The Windows Report procedure describes using Microsoft’s Media Creation Tool for supported Windows installations.
Recommended Free Tools
- Back up critical data and confirm that you have enough storage and the correct edition and language media.
- Disconnect nonessential peripherals and temporarily pause third-party software that could interfere with setup.
- Start the installation media from within Windows, not by booting directly, when you intend to preserve apps and files.
- When setup offers the choice, select the option to keep personal files and apps. If that option is unavailable, stop; proceeding would be a different, more destructive installation.
- Allow multiple restarts and keep the device connected to reliable power.
- After setup completes, install pending updates and recheck the service configuration.
Media Creation Tool availability and supported editions vary. Windows Server editions do not necessarily use the same workflow as client Windows, so verify the method for your exact Server release and licensing channel before starting. A repair upgrade is more disruptive than a service restart and should be treated as a last-resort repair, not a first response to an incomplete code.
Common mistakes and how to avoid them
- Assuming the missing digit. Searching for 0x8007042 and immediately applying a 0x80070422 guide can change update services when the real problem is the firewall. Capture the complete code first.
- Changing every service to Automatic. Windows uses demand-start and policy-controlled services. Change only the service implicated by the symptom and restore the previous setting if testing disproves the theory.
- Skipping administrator elevation. SFC, DISM,
sc config, and cache renames can fail silently or return access errors without elevation. - Deleting caches instead of renaming them. Renaming preserves evidence and gives Windows a clean folder to rebuild. Deletion removes that fallback.
- Running a repair upgrade without checking the keep-options. If setup cannot keep apps and files, cancel and investigate edition, language, and media mismatches.
- Ignoring managed-device policy. Domain policies and security baselines can disable services again. Coordinate with the administrator rather than repeatedly applying local changes.
When to escalate
Escalate to your organization’s administrator or Microsoft support channel when the complete code changes after every restart, a service is locked by policy, DISM cannot repair the component store, or the machine is a production server with dependent workloads. Provide the full hexadecimal code, the failing component, Windows edition and build, service-status screenshots or text, and the final SFC/DISM messages. That information is more useful than reporting only “server 0x8007042.”
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues, including broken system elements and shared DLL problems, and includes cleanup, settings adjustments, vulnerability checks and an app-crash log. It runs on Windows 11, 10, 8 and 7 and offers a free trial by category for at least two days before a subscription; it complements antivirus software rather than replacing it, results vary, and 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.
