Recommended Free Tools
Error 0x0000138D is Windows’ ERROR_HOST_NODE_NOT_AVAILABLE status. It is a symbolic system error, not a diagnosis of one universal consumer problem. The operation that produced it—such as an update, installation, application launch, or crash—and the event recorded at the same time determine the correct remedy.
Start by recording exactly what you were doing, then inspect Event Viewer for the event and any named device, driver, or module. Use the branch below that matches the trigger: Windows Update, setup or upgrade, or a crash, restart, or blue screen. These steps apply to Windows 11 and Windows 10, although menu wording can differ slightly by release.
As an Amazon Associate I earn from qualifying purchases.
What 0x0000138D means
Microsoft’s Windows error reference assigns hexadecimal code 0x0000138D to ERROR_HOST_NODE_NOT_AVAILABLE. The name indicates that a host node expected by some operation was unavailable. It does not identify which application, service, device, or driver was involved, and it does not by itself prove that Windows is damaged.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The same code can therefore appear in unrelated situations. An updater may report it while contacting or starting a component; an installer may show it while preparing a setup task; an application may log it before closing; and a system failure may display it alongside a stop error. Treat the code as a clue, not as a complete diagnosis.
#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
Choose the right troubleshooting path first
Use the event that occurred immediately before the code to select your first action. Do not begin by deleting files, changing the registry, or downloading a replacement DLL when you do not yet know which component failed.
| Where you saw 0x0000138D | First priority | Evidence to collect |
|---|---|---|
| Windows Update or an update restart | Run the Windows Update troubleshooter, restart, and check for updates again. | Update name or KB, time of failure, and the related System or Windows Update event. |
| Program installation, Windows setup, or an upgrade | Disconnect nonessential hardware, then apply Microsoft’s general installation and upgrade fixes. | Installer or setup name, Windows edition and build, and any setup-log error. |
| Application crash without a blue screen | Capture the application event and identify the failing module before changing drivers or software. | Application name, faulting module, timestamp, and the matching System event. |
| Restart, blue screen, or stop error | Remove recently added hardware, test Safe Mode, and investigate the named driver or module. | Stop-code text, minidump or event details, hardware changes, and driver name. |
Step 1: Capture context before changing Windows
Write down the triggering action
Record the application, command, update, installer, or device action that produced the message. Include whether the operation was a first-time install, a repair, an upgrade, or a routine update. Note whether Windows remained usable, froze, restarted, or displayed a blue screen. If the message appeared only once, write down the exact time and the wording around the code; a screenshot is useful when the dialog disappears.
Also note changes made shortly beforehand: a newly connected printer or USB drive, a graphics or audio device, a docking station, a driver installation, or a newly installed program. A time relationship does not prove causation, but it gives Event Viewer a concrete window to inspect.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Open Event Viewer and find the matching event
- Press Windows key+X and select Event Viewer. You can also search for “Event Viewer” from Start.
- In the left pane, open Windows Logs, then select System. If the message came from a particular application, also inspect Application and that program’s own log under Applications and Services Logs.
- Sort or scan the entries around the time you recorded. Look for an Error or Critical event immediately before or after the code.
- Open the event and read the General and Details tabs. Record the event ID, source, application or service name, device, driver, and module mentioned.
- Use Copy from the event’s shortcut menu to preserve the full text. Keep the original timestamp and computer name with the copy.
Microsoft advises checking the System log because nearby messages can identify a device or driver. One event rarely tells the whole story; a sequence of warnings followed by the error is often more useful than the hexadecimal code alone.
If Windows Update triggered the code
Run the built-in troubleshooter
On Windows 11, Microsoft directs users to the automated Windows Update troubleshooter in the Get Help app. Open Start, search for Get Help, launch it, and follow the Windows Update prompts. Allow the app to apply a suggested correction, then close it when it reports that the checks are complete.
You can also reach the built-in troubleshooter through the settings interface: open Start > Settings > System > Troubleshoot > Other troubleshooters, find Windows Update, and select Run. Windows 10 uses different Settings groupings in some releases; search Settings for “Troubleshoot settings” and choose the Windows Update troubleshooter if the System path is not shown.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Restart, then check again
- Save your work and restart Windows normally. A restart is required for some servicing changes and clears a failed update session.
- After signing in, open Start > Settings > Windows Update on Windows 11. On Windows 10, open Start > Settings > Update & Security > Windows Update.
- Select Check for updates. Install the offered update and restart if Windows requests it.
- If the same code returns, capture the new timestamp and event details instead of repeatedly selecting Check for updates. The second event may name the component that the first attempt did not expose.
The troubleshooter is appropriate when the code is tied to update detection or installation. It is not a general repair for an unrelated application crash; use the branch that matches the operation.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If setup, installation, or an upgrade triggered it
Strip the setup down to essential hardware
Shut down the computer if the installer is no longer responsive. Disconnect nonessential external devices, including printers, scanners, speakers, USB drives, and external disks. If you are using a laptop, undock it from the docking station. Leave only the input devices and hardware required to operate the system and complete setup.
Reconnect devices one at a time after the installation or upgrade succeeds. This creates a clear test: if the code returns when a particular device is attached, its driver or firmware becomes a focused investigation rather than a guess about the entire computer.
Apply the general installation guidance
Run Microsoft’s general fixes for Windows installation and upgrade failures that match your situation, and follow their prerequisites exactly. Do not assume that an error shown by an installer is an update error; setup logs can contain a different underlying failure. If the code persists, review the setup logs for the timestamp you recorded and preserve the relevant error lines for the software or hardware vendor.
When setup fails after hardware removal, restore only the essential configuration and repeat the operation once. Repeated attempts with every peripheral attached can produce a different log each time and make the original failure harder to identify.
If a crash, restart, or blue screen accompanied 0x0000138D
Remove recent hardware changes
Disconnect or remove hardware added immediately before the problem, following the device manufacturer’s safe-removal instructions. If Windows becomes stable after the change, leave the device disconnected while you identify its driver or firmware. Do not infer that the device is defective solely from the timing; the event may instead identify an incompatible or corrupted driver.
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Test in Safe Mode
Safe Mode starts Windows with a limited set of drivers and services. If the failure does not occur there, a normally loaded driver, service, or startup program becomes more likely than a basic Windows boot component.
- Open Start > Settings > System > Recovery on Windows 11, or the corresponding Recovery page in Windows 10.
- Under Advanced startup, select Restart now. You can also hold Shift while selecting Restart from the power menu.
- At the recovery menu, choose Troubleshoot > Advanced options > Startup Settings > Restart.
- When the numbered choices appear, press 4 or F4 for Safe Mode. Choose the networking option only when you specifically need network access for a diagnostic task.
- Repeat the action that caused the error only if it is safe to do so, and note whether the crash or restart returns.
If Windows fails in Safe Mode as well, hardware, core system components, or a driver loaded in that mode deserve priority. If Safe Mode is stable, return to normal startup and use the event details to isolate the added driver or software instead of uninstalling unrelated programs at random.
Follow a named driver or module
When the event or stop message names a driver or module, use that name as the investigation anchor. Microsoft’s guidance for stop errors is to consider hardware, a device driver, or software as possible causes and follow the named-driver path when one is identified. Check which physical device owns the driver, then use the device manufacturer’s current official package or the approved rollback option if the problem began immediately after an update.
Record the driver version before changing it. If an update resolves the crash, keep the old event and the new version in your notes; if it does not, restore the previous state when possible and continue with the next named component. Avoid replacing a system file with a DLL downloaded from an unrelated website.
Read the logs as a sequence, not a single line
Event Viewer can show several entries for one failure. Start with the timestamp and read a few minutes before and after it. A service timeout, device disconnect, or driver warning before the 0x0000138D entry may explain why the host node was unavailable. An application error immediately afterward may be a consequence rather than the cause.
Compare the Source, Event ID, and named module across repeated attempts. If every occurrence identifies the same driver, focus on that device. If different applications report the code but the same system event appears underneath, investigate the shared device or service. If only one application reports it and the System log is quiet, the application vendor needs the application event and its module details.
Rank #4
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
What to do when the problem disappears
A single occurrence that does not return after a restart may have been a transient operation failure, but keep the captured event until the related update, installation, or application has worked normally several times. Reconnect removed peripherals one at a time and test after each connection. This controlled order is safer than reconnecting everything together because it preserves the ability to identify a trigger.
If an update succeeds but the code later appears during a different operation, start a new context record. The hexadecimal value is the same, but the failing subsystem may not be. Do not carry assumptions from an earlier update failure into an unrelated application crash.
When to escalate
Escalate to Microsoft support or the software or hardware vendor when the code repeats after the appropriate branch has been completed, when Windows cannot remain stable long enough to diagnose it, or when a named driver continues to fail after the vendor’s current package and documented rollback options have been tried.
Include a concise evidence bundle:
- The exact 0x0000138D text and any accompanying stop-code message.
- The application, command, update, installer, or device action that triggered it.
- The date and time, time zone, and whether Windows stayed usable, restarted, or showed a blue screen.
- Windows edition, version, and build number.
- Event Viewer source, event ID, full message, and any named driver, device, service, or module.
- Hardware or software changes made immediately before the first occurrence.
- The troubleshooting steps already completed and their results, including whether Safe Mode changed the behavior.
This information lets a support engineer reproduce the same path and distinguish a host-node availability message from the component that actually failed.
Common dead ends to avoid
- Treating the code as a universal diagnosis: the symbolic name does not identify the application or subsystem.
- Running update repairs for an application crash: choose the path from the operation that produced the message.
- Leaving every peripheral attached during setup: nonessential devices add drivers and variables to the installation; disconnect them first.
- Changing several drivers at once: one change at a time preserves a useful cause-and-effect record.
- Deleting registry entries or downloading replacement system files: those actions can remove evidence or create new failures without addressing the named event.
- Reporting only “Windows error” to support: the timestamp, event ID, module, and trigger are substantially more actionable.
Because no authoritative prevalence statistic or success rate has been established for 0x0000138D, a claimed percentage fix or frequency would be misleading. The reliable approach is to connect the code to its operation and the surrounding Windows event, then apply the matching built-in procedure.
Quick Recap
As an optional shortcut after these manual steps, Outbyte PC Repair can look for more than 100 common Windows issues where possible, including broken system elements, invalid redirects, and shared DLL problems, while also offering settings tweaks, temporary-file cleanup, privacy warnings, vulnerability checks, a real-time boost, file shredding, and an app-crash log. It runs on Windows 11, 10, 8, and 7; its free trial lasts at least two days before a paid subscription, and it complements rather than replaces antivirus protection. Results vary, and no repair tool fixes 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.
