<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OhSudo — new Windows articles</title><description>New Windows articles from OhSudo: practical fixes for DevOps engineers, SysAdmins and IT folks.</description><link>https://ohsudo.com/</link><language>en-us</language><atom:link href="https://ohsudo.com/rss/windows.xml" rel="self" type="application/rss+xml"/><item><title>Windows Update error 0x80070643: find which update failed, then fix that one</title><link>https://ohsudo.com/articles/windows-update-error-0x80070643/</link><guid isPermaLink="true">https://ohsudo.com/articles/windows-update-error-0x80070643/</guid><description>Fix Windows Update error 0x80070643: find the failing update, repair the component store, reset Windows Update, and handle the WinRE partition and .NET cases.</description><pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows-update</category><category>dism</category><category>sfc</category><category>winre</category><category>windows-server</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Hyper-V &quot;the hypervisor is not running&quot;: turn it on, in the firmware and at boot</title><link>https://ohsudo.com/articles/hyper-v-hypervisor-is-not-running/</link><guid isPermaLink="true">https://ohsudo.com/articles/hyper-v-hypervisor-is-not-running/</guid><description>Fix Hyper-V &quot;Virtual machine could not be started because the hypervisor is not running&quot;: enable virtualization in the firmware, set hypervisorlaunchtype to auto.</description><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>hyper-v</category><category>windows-server</category><category>virtualization</category><category>bcdedit</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Windows &quot;The specified domain either does not exist or could not be contacted&quot;: it&apos;s usually DNS</title><link>https://ohsudo.com/articles/windows-specified-domain-does-not-exist-could-not-be-contacted/</link><guid isPermaLink="true">https://ohsudo.com/articles/windows-specified-domain-does-not-exist-could-not-be-contacted/</guid><description>Fix &quot;The specified domain either does not exist or could not be contacted&quot; when joining a domain: point DNS at a domain controller, test the SRV records, ports and time.</description><pubDate>Mon, 09 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>active-directory</category><category>windows-server</category><category>dns</category><category>domain-join</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>PowerShell &quot;is not recognized as the name of a cmdlet&quot;: find out why it can&apos;t see the command</title><link>https://ohsudo.com/articles/powershell-is-not-recognized-as-the-name-of-a-cmdlet/</link><guid isPermaLink="true">https://ohsudo.com/articles/powershell-is-not-recognized-as-the-name-of-a-cmdlet/</guid><description>Fix PowerShell &quot;is not recognized as the name of a cmdlet, function, script file&quot;: check the spelling, PATH, the .\ prefix for scripts and missing modules, step by step.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>powershell</category><category>windows</category><category>path</category><category>modules</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>DISM error 0x800f081f &quot;The source files could not be found&quot;: give Windows a matching source</title><link>https://ohsudo.com/articles/dism-0x800f081f-source-files-could-not-be-found/</link><guid isPermaLink="true">https://ohsudo.com/articles/dism-0x800f081f-source-files-could-not-be-found/</guid><description>Fix DISM /RestoreHealth error 0x800f081f &quot;The source files could not be found&quot;: point it at a matching install.wim, allow Windows Update, and repair with SFC afterwards.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows-server</category><category>dism</category><category>sfc</category><category>windows-update</category><category>repair</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>IIS &quot;HTTP Error 500.19&quot; and &quot;503 Service Unavailable&quot;: read the code, then fix web.config or the app pool</title><link>https://ohsudo.com/articles/iis-http-error-500-19-503-service-unavailable/</link><guid isPermaLink="true">https://ohsudo.com/articles/iis-http-error-500-19-503-service-unavailable/</guid><description>Fix IIS &quot;HTTP Error 500.19&quot; by its error code (a missing module, a bad web.config, permissions) and &quot;503 Service Unavailable&quot; by finding why the app pool stopped.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>iis</category><category>windows-server</category><category>web-config</category><category>asp-net</category><category>app-pool</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Windows &quot;System error 53&quot; and &quot;System error 5&quot; with net use: the network path, and access denied</title><link>https://ohsudo.com/articles/windows-system-error-53-net-use/</link><guid isPermaLink="true">https://ohsudo.com/articles/windows-system-error-53-net-use/</guid><description>Fix net use &quot;System error 53: The network path was not found&quot; and &quot;System error 5: Access is denied&quot;: check DNS, ports 445 and 139, the share and your credentials.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows-server</category><category>smb</category><category>net-use</category><category>file-sharing</category><category>firewall</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>PowerShell &quot;running scripts is disabled on this system&quot;: fix the execution policy safely</title><link>https://ohsudo.com/articles/powershell-running-scripts-is-disabled/</link><guid isPermaLink="true">https://ohsudo.com/articles/powershell-running-scripts-is-disabled/</guid><description>Fix PowerShell &quot;cannot be loaded because running scripts is disabled&quot;: check the execution policy, use RemoteSigned for your user, and unblock downloaded scripts.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows</category><category>powershell</category><category>execution-policy</category><category>scripts</category><category>npm</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>RDP &quot;An authentication error has occurred&quot;: CredSSP encryption oracle and other causes</title><link>https://ohsudo.com/articles/rdp-authentication-error-credssp-encryption-oracle/</link><guid isPermaLink="true">https://ohsudo.com/articles/rdp-authentication-error-credssp-encryption-oracle/</guid><description>Fix Remote Desktop &quot;An authentication error has occurred&quot; and &quot;CredSSP encryption oracle remediation&quot;: update both machines, check NLA, passwords, time and port 3389.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows</category><category>windows-server</category><category>rdp</category><category>remote-desktop</category><category>credssp</category><category>security</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Windows &quot;The RPC server is unavailable&quot; (0x800706BA): how to find what blocks it</title><link>https://ohsudo.com/articles/windows-rpc-server-is-unavailable-0x800706ba/</link><guid isPermaLink="true">https://ohsudo.com/articles/windows-rpc-server-is-unavailable-0x800706ba/</guid><description>Fix &quot;The RPC server is unavailable&quot; (0x800706BA, error 1722): check the name, port 135, the dynamic ports, the firewall rules and the RPC services, step by step.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows-server</category><category>rpc</category><category>wmi</category><category>active-directory</category><category>firewall</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Windows &quot;The trust relationship between this workstation and the primary domain failed&quot;: fix it without rejoining</title><link>https://ohsudo.com/articles/windows-trust-relationship-primary-domain-failed/</link><guid isPermaLink="true">https://ohsudo.com/articles/windows-trust-relationship-primary-domain-failed/</guid><description>Fix &quot;The trust relationship between this workstation and the primary domain failed&quot;: repair the computer account password with PowerShell, without rejoining the domain.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>windows</category><category>windows-server</category><category>active-directory</category><category>powershell</category><category>domain</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>WSL &quot;WslRegisterDistribution failed with error: 0x80370102&quot;: turn on virtualization</title><link>https://ohsudo.com/articles/wsl-wslregisterdistribution-failed-0x80370102/</link><guid isPermaLink="true">https://ohsudo.com/articles/wsl-wslregisterdistribution-failed-0x80370102/</guid><description>Fix WSL &quot;WslRegisterDistribution failed with error: 0x80370102&quot;: enable virtualization in the firmware, Virtual Machine Platform, the hypervisor or nested virtualization.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Windows</category><category>wsl</category><category>windows</category><category>hyper-v</category><category>virtualization</category><category>ubuntu</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item></channel></rss>