Recommended Free Tools
If Windows Server 2016 reports 0x80070042, Windows is mapping the failure to ERROR_BAD_DEV_TYPE: “The network resource type is not correct.” The code usually points to a share, mapped drive, network provider, endpoint, or related service configuration—not automatically to damaged Windows Update files.
The title’s 0X800700422 contains one extra trailing “2” compared with the documented value. First verify the exact hexadecimal code in the event, Windows Update screen, or application log. If the system really reports 0x800700422, identify the component that emitted it before applying the procedure below; the documented references for this issue cover 0x80070042, not the longer value.
As an Amazon Associate I earn from qualifying purchases.
What 0x80070042 means on Windows Server 2016
Windows error values beginning with 0x8007 commonly wrap a Win32 error. In this case, 0x80070042 maps to ERROR_BAD_DEV_TYPE, whose message is “The network resource type is not correct.” Windows has reached an operation that expects one kind of network resource but received another, or a provider cannot interpret the target as the expected resource.
That can happen while Windows Update contacts an update service, when a scheduled task accesses a UNC path, when a service uses a mapped drive, or when an application opens a share through a network provider. The code alone does not identify the exact target, account, provider, or service that failed.
#1 Best Overall
Why the exact context matters
- A path such as
\servershare, a mapped drive letter, and a provider-specific resource are not interchangeable in every service or task context. - A share can work for an administrator signed in interactively but fail for a scheduled task or Windows service running under another account.
- Name resolution, permissions, unavailable servers, and disabled network services can all produce symptoms around the same operation.
- The appearance of this code does not, by itself, establish Windows component-store corruption or justify servicing repair.
Step 1: Confirm the code and record the failure
Do not change system settings until you know which component generated the message. Record the code exactly as shown, including every hexadecimal digit and any leading zero.
- Open the screen or log that displayed the error. For Windows Update, note the update attempt time and the complete text around the code.
- In Event Viewer, open Windows Logs and review System and Application around that timestamp. If the issue involves updates, also inspect the relevant Windows Update and servicing events.
- Write down the failing executable, service, scheduled task, update, script, or application; the target server or share; and the account that was running it.
- Save the complete event details before clearing logs or retrying. The event’s provider, event ID, path, and account often identify the real fix more precisely than the hexadecimal code.
If the value is genuinely 0x800700422, stop here and trace its emitting component. Do not assume that the documented meaning of 0x80070042 applies to a different value.
Step 2: Check the network resource, path, and provider
Once you have identified the target, verify that it is the resource type the operation expects.
Validate the target path
- For a file share, confirm the UNC path uses the expected server and share name, for example
\servershare. Check for spelling errors, stale drive letters, and scripts that refer to a share that was renamed or removed. - From the affected server, test the same target interactively with an account that is supposed to have access. A successful test proves only that this account and session can reach it; it does not prove that a service account can.
- If the operation uses a mapped drive, check whether the mapping exists in the same logon session. Mapped drives created for an interactive user are often unavailable to services and scheduled tasks.
- If a third-party or Windows network provider is involved, verify that the provider is installed, enabled, and intended for this resource type. A provider mismatch can make a valid-looking path appear to be the wrong kind of network resource.
Check name resolution and connectivity
Confirm that the server name resolves to the expected address and that the required network route and service port are reachable from Windows Server 2016. Use your organization’s approved DNS and connectivity checks, then compare the result from the affected server with a known-good machine. A successful ping is not proof that file-sharing or the application protocol is available, so test the actual service used by the operation.
Verify access for the running account
Check both share-level and NTFS permissions where applicable. Confirm that the account has the required read, write, or administrative rights and that a deny entry, expired password, locked account, or domain trust problem is not intervening. Document whether the failure occurs only under a scheduled-task or service account; that distinction is a major diagnostic clue.
Step 3: Inspect Network List Service and dependencies
A Microsoft Q&A user reported that Windows Update stopped showing 0x80070042 after changing Network List Service from Disabled to Manual and starting it. This is an anecdotal user report, not a Microsoft-supported universal fix, but it is a useful lead when the service is disabled.
- Sign in with an account that can administer services, and open
services.msc. - Locate Network List Service. Record its current startup type and service status before changing anything.
- If it is Disabled, consider changing the startup type to Manual, then select Start. Make this change during an approved maintenance window and document the original setting.
- Open the service’s Dependencies tab. Check that required networking services are present and are not disabled. Do not broadly change unrelated services based only on this error code.
- Retry the exact operation that failed. If it succeeds, retain the before-and-after service state and the event timestamp so the change can be reviewed or reversed.
If Network List Service was already running, its state is unlikely to be the sole explanation. Continue with the target, provider, account, and log checks instead of repeatedly restarting services.
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 →Step 4: Compare interactive, scheduled-task, and service behavior
Windows Server often performs the same action under different security contexts. A task that works when launched manually can fail when the Task Scheduler or a service launches it.
- Open Task Scheduler and inspect the task’s History, Actions, Conditions, and Security options. Note the configured user, whether the task runs whether or not the user is logged on, and its working directory.
- For a Windows service, open its Log On tab and record the account. Verify that this account can resolve and access the target without relying on a user’s mapped drive.
- Run a controlled test using the same account and the same path, following your organization’s security procedures. Do not expose passwords or weaken least-privilege controls merely to make the test pass.
- Compare the successful interactive run with the failed scheduled or service run. Differences in environment variables, drive mappings, network availability at startup, and permissions usually reveal the cause.
Step 5: Retry once, then collect the relevant logs
After correcting an obvious path, permission, provider, or service-state issue, reproduce the failure once. Record the exact time and retain the resulting events.
- Event Viewer: save the System, Application, and provider-specific entries surrounding the retry.
- Windows Update: retain the Windows Update and servicing events if the error appeared during an update check or installation.
- Task Scheduler: export or record the task history, result code, action, and account.
- Application logs: capture the executable’s own error text, target path, and configuration details.
Compare the new event with the original. If the code changes, the failing component changes, or the error occurs only under one account, those observations are more actionable than repeatedly applying unrelated repairs.
When DISM and SFC are appropriate
Microsoft’s general update guidance uses Deployment Image Servicing and Management (DISM) with /RestoreHealth, followed by System File Checker (SFC), for evidence of component-store or protected-system-file corruption. The common-error guidance does not identify 0x80070042 as a component-store code, so servicing repair should not be the default response to this message.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use servicing repair only when logs support it
Consider these commands when servicing events, update errors, or system-file checks point to corruption, and schedule the work for a suitable maintenance window:
Best Value
- Open Command Prompt (Admin) or an equivalent elevated console.
- Run
DISM /Online /Cleanup-Image /RestoreHealthand allow it to finish. Do not interrupt the operation because progress may pause for an extended period. - After DISM completes, run
sfc /scannow. - Review the result, reboot if Windows or your change-management process requires it, and retry the original operation.
- If the network-resource error remains while servicing checks are clean, return to the path, provider, account, and service investigation rather than repeating DISM and SFC.
On a production server, confirm backup and rollback procedures before servicing the operating image. These commands repair Windows components when corruption is present; they do not convert an incorrect share or provider into the expected network-resource type.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose the least invasive correction first
| Correction path | Evidence required | Change scope | Reboot or downtime | Reversibility | Recurrence under the same account |
|---|---|---|---|---|---|
| Network List Service state | Service is disabled or dependency state is abnormal; the reported user case involved Windows Update | One service’s startup type and status | Not stated in the available report; test during a maintenance window | Record the original setting and restore it if testing disproves the lead | Recur if the underlying resource, provider, or account issue remains |
| Network-resource or path correction | Wrong share, mapped drive, provider, DNS result, route, or permission identified | Target path, provider configuration, DNS/network access, or permissions | Depends on the resource owner; the available guidance does not prescribe a universal outage | Usually reversible when the original path and settings are documented | Should stop recurring for the corrected account and target; test other accounts separately |
| Windows servicing repair | Servicing logs or checks show component-store or protected-file corruption | Windows component store and protected system files | May take substantial time and can require a reboot; schedule maintenance | Use established server backup and rollback procedures | Will not prevent recurrence caused by a wrong network resource or account context |
Common mistakes to avoid
- Fixing the wrong code: treating 0x800700422 as 0x80070042 without verifying the event can send troubleshooting in the wrong direction.
- Assuming Windows Update corruption: the code’s documented mapping concerns a network-resource type; update symptoms do not prove component corruption.
- Using a drive letter in a service: a drive mapped for one user session may not exist for a service or scheduled task.
- Changing many services at once: broad changes destroy the ability to identify the cause and can create new failures.
- Testing only as an administrator: administrator access can hide the permissions or authentication problem affecting the real account.
- Repeating DISM and SFC without evidence: servicing commands cannot correct a malformed share path, provider mismatch, DNS failure, or missing account permission.
- Clearing evidence too early: preserve the original event, timestamp, provider, path, and account before retrying.
When to escalate
Escalate to the team that owns the affected resource when the target server, share, provider, DNS record, firewall policy, or permissions are outside your control. Provide the exact code, complete event text, timestamp, target, running account, service state, and a comparison of interactive versus scheduled or service execution.
Escalate to Windows servicing support when the code is confirmed as 0x80070042 but component-store events independently show corruption, or when DISM and SFC report failures that require source media or a repair installation. If the code remains unexplained after the resource and account checks, do not infer a universal fix from a single anecdotal report.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Optional shortcut
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, and includes settings, cleanup, vulnerability-check, real-time-boost, file-shredder, and app-crash-log features. It runs on Windows 11, 10, 8, and 7; a free trial is available by category for at least two days before a paid subscription. It complements an antivirus rather than replacing one, results vary, and no tool repairs every crash or network configuration problem.
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.
