{"id":248,"date":"2026-11-22T15:22:38","date_gmt":"2026-11-22T13:22:38","guid":{"rendered":"https:\/\/vladimir-shapiro.com\/en\/blog\/?p=248"},"modified":"2026-11-22T15:58:26","modified_gmt":"2026-11-22T13:58:26","slug":"windows-11-automatic-repair-loop-on-lenovo-machine-after-an-update-a-fix-for-pxhlpa64-sys","status":"publish","type":"post","link":"https:\/\/vladimir-shapiro.com\/en\/blog\/2026\/11\/22\/windows-11-automatic-repair-loop-on-lenovo-machine-after-an-update-a-fix-for-pxhlpa64-sys\/","title":{"rendered":"Windows 11 automatic repair loop on Lenovo machine after an update \u2014 A Fix for PxHlpa64.sys"},"content":{"rendered":"<h2>I&#8217;m so glad Microsoft keeps me technologically fit.<\/h2>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignleft size-full wp-image-262\" src=\"http:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140841.png\" alt=\"\" width=\"902\" height=\"455\" srcset=\"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140841.png 902w, https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140841-300x151.png 300w, https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140841-768x387.png 768w, https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140841-624x315.png 624w\" sizes=\"(max-width: 902px) 100vw, 902px\" \/><\/p>\n<p>Here&#8217;s how I spent Sunday morning instead of preparing the tax paperwork for my home, as planned: troubleshooting a Windows 11 boot loop, digging through recovery logs, and eventually disabling a DVD driver from 2013.<\/p>\n<p>Apparently, keeping a Windows PC running is a great way to prevent your troubleshooting skills from getting rusty.<\/p>\n<p><strong>Long story short:<\/strong> A Windows 11 computer became stuck in an endless Automatic Repair loop following the November 2026 Windows updates. The problem was traced to an outdated optical-disc driver, <code>PxHlpa64.sys<\/code>, dating from 2013. Disabling the driver restored Windows startup. Removing its obsolete <code>LowerFilters<\/code> reference subsequently restored the DVD drive.<\/p>\n<p>The issue was resolved on a <strong>Lenovo ThinkStation running Windows 11<\/strong>, without reinstalling Windows or losing personal files.<\/p>\n<p>Similar failures have been reported following the November 10, 2026 security update <strong>KB5132061<\/strong>, although the exact update responsible for this particular incident could not be conclusively identified.<\/p>\n<p><!--more--><\/p>\n<h3>Symptoms and failed recovery attempts<\/h3>\n<p>Following a Windows Update on November 21, 2026, the machine repeatedly entered Automatic Repair. Windows could not start normally or in Safe Mode.<\/p>\n<p>The recovery log <code>SrtTrail.txt<\/code> reported:<\/p>\n<pre><code>A recently processed boot binary is corrupt.\nRepair action: Uninstall latest LCU\nResult: Failed, error 0x905<\/code><\/pre>\n<p>The following recovery procedures were attempted without success:<\/p>\n<ul>\n<li>Automatic Startup Repair<\/li>\n<li>Safe Mode<\/li>\n<li>System Restore to a point before the failure<\/li>\n<li>Uninstalling the latest Windows quality update<\/li>\n<li>System File Checker (SFC), which found no integrity violations<\/li>\n<\/ul>\n<h3>The likely root cause: an old boot-start driver<\/h3>\n<p>Further investigation identified:<\/p>\n<pre><code>C:\\Windows\\System32\\drivers\\PxHlpa64.sys<\/code><\/pre>\n<p>This driver is associated with the legacy PxEngine software used by older CD\/DVD recording applications, including products based on Sonic\/Roxio technology.<\/p>\n<p>The installed file was dated September 3, 2013. More importantly, its Windows registry configuration showed:<\/p>\n<pre><code>Start    REG_DWORD    0x0\nGroup    REG_SZ       Filter<\/code><\/pre>\n<p><strong>Start = 0<\/strong> means the driver is loaded very early during Windows startup. An incompatible driver at this stage can interfere with booting, even before Safe Mode becomes available.<\/p>\n<p>Similar cases involving <code>PxHlpa64.sys<\/code> have been reported following Windows 11 updates, including KB5132061. In this case, disabling the driver immediately restored Windows startup, strongly implicating it in the failure.<\/p>\n<h3>Fix 1 \u2014 Disable PxHlpa64.sys from Windows Recovery<\/h3>\n<p><strong>Warning:<\/strong> This procedure modifies the Windows registry. It should only be used if the same driver is present and registered on the affected computer. Back up important data where possible. Incorrect registry changes can prevent Windows from starting.<\/p>\n<h4>Step 1 \u2014 Open Command Prompt in Windows Recovery<\/h4>\n<p>Navigate to:<\/p>\n<pre><code>Troubleshoot \u2192 Advanced options \u2192 Command Prompt<\/code><\/pre>\n<h4>Step 2 \u2014 Load the offline Windows registry<\/h4>\n<p>The examples assume Windows is installed on <code>C:<\/code>. Verify the correct drive letter first, since it may differ in the recovery environment.<\/p>\n<pre><code>reg load HKLM\\OFFSYS C:\\Windows\\System32\\Config\\SYSTEM<\/code><\/pre>\n<p>This makes the registry of the non-booting Windows installation accessible for inspection and repair.<\/p>\n<h4>Step 3 \u2014 Determine the active control set<\/h4>\n<pre><code>reg query HKLM\\OFFSYS\\Select \/v Current<\/code><\/pre>\n<p>In this case, the result was <code>0x1<\/code>, corresponding to <code>ControlSet001<\/code>. If your value is different, use the corresponding control set in the following commands.<\/p>\n<h4>Step 4 \u2014 Check the driver startup configuration<\/h4>\n<pre><code>reg query \"HKLM\\OFFSYS\\ControlSet001\\Services\\PxHlpa64\" \/v Start<\/code><\/pre>\n<p>The result was:<\/p>\n<pre><code>Start    REG_DWORD    0x0<\/code><\/pre>\n<p>If the driver service does not exist, this particular fix may not apply.<\/p>\n<h4>Step 5 \u2014 Back up the driver settings<\/h4>\n<pre><code>reg export \"HKLM\\OFFSYS\\ControlSet001\\Services\\PxHlpa64\" C:\\PxHlpa64_backup.reg \/y<\/code><\/pre>\n<h4>Step 6 \u2014 Disable the driver<\/h4>\n<pre><code>reg add \"HKLM\\OFFSYS\\ControlSet001\\Services\\PxHlpa64\" \/v Start \/t REG_DWORD \/d 4 \/f<\/code><\/pre>\n<p>This changes the startup setting from <code>0<\/code> (Boot Start) to <code>4<\/code> (Disabled).<\/p>\n<p><strong>In simple terms:<\/strong> Windows is instructed to stop loading this old driver during startup. The driver file remains on disk, and the change can be reversed if necessary.<\/p>\n<p>Verify that <code>Start<\/code> is now <code>0x4<\/code>:<\/p>\n<pre><code>reg query \"HKLM\\OFFSYS\\ControlSet001\\Services\\PxHlpa64\" \/v Start<\/code><\/pre>\n<p>Then unmount the registry:<\/p>\n<pre><code>reg unload HKLM\\OFFSYS<\/code><\/pre>\n<p>Restart Windows normally.<\/p>\n<p><strong>Result: Windows successfully booted.<\/strong> Multiple subsequent restarts also worked.<\/p>\n<h3>Fix 2 \u2014 Restore the DVD drive by removing LowerFilters<\/h3>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignleft size-full wp-image-263\" src=\"http:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140454.png\" alt=\"\" width=\"685\" height=\"437\" srcset=\"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140454.png 685w, https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140454-300x191.png 300w, https:\/\/vladimir-shapiro.com\/en\/blog\/wp-content\/uploads\/Screenshot-2026-11-22-140454-624x398.png 624w\" sizes=\"(max-width: 685px) 100vw, 685px\" \/><\/p>\n<p>After Windows was restored, Device Manager displayed a yellow warning icon for the DVD drive:<\/p>\n<blockquote><p>A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)<\/p><\/blockquote>\n<p>The problem was that the DVD drive still referenced <code>PxHlpa64<\/code>, even though the driver had been disabled.<\/p>\n<blockquote><p><strong>What are LowerFilters, and why can they be removed?<\/strong><\/p>\n<p>Windows uses a standard driver to communicate with a DVD drive. Additional software can install optional <strong>filter drivers<\/strong> to add functions such as disc burning or other optical-media features.<\/p>\n<p><code>LowerFilters<\/code> is a Windows registry setting listing additional drivers that operate below the main device driver in the device stack.<\/p>\n<p>In this case, the DVD device class contained only <code>PxHlpa64<\/code>. Because that driver had been disabled, Windows could no longer load the filter, resulting in Device Manager error Code 32.<\/p>\n<p>Removing the reference was appropriate because it pointed exclusively to the obsolete, disabled driver. The standard Microsoft DVD driver did not depend on it.<\/p>\n<p><strong>Important:<\/strong> Removing <code>LowerFilters<\/code> is not universally safe. Other systems may contain additional filter drivers required by installed software. Always inspect the value before deleting it. Some specialized disc-burning functions may stop working even when the DVD drive itself works normally.<\/p><\/blockquote>\n<h4>Step 1 \u2014 Check the existing LowerFilters value<\/h4>\n<p>Once Windows starts successfully, open <strong>Terminal (Admin)<\/strong> and run:<\/p>\n<pre><code>reg.exe query \"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Class\\{4D36E965-E325-11CE-BFC1-08002BE10318}\" \/v LowerFilters<\/code><\/pre>\n<p>In this case, the only entry was <code>PxHlpa64<\/code>.<\/p>\n<h4>Step 2 \u2014 Back up the DVD class registry settings<\/h4>\n<pre><code>reg.exe export \"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Class\\{4D36E965-E325-11CE-BFC1-08002BE10318}\" \"C:\\DVD_Class_Backup.reg\" \/y<\/code><\/pre>\n<h4>Step 3 \u2014 Remove the obsolete LowerFilters value<\/h4>\n<p><strong>Only proceed if LowerFilters contains exactly PxHlpa64 and no other drivers.<\/strong><\/p>\n<pre><code>reg.exe delete \"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Class\\{4D36E965-E325-11CE-BFC1-08002BE10318}\" \/v LowerFilters \/f<\/code><\/pre>\n<p>This removes the registry value, not the entire registry key and not the DVD device driver.<\/p>\n<h4>Step 4 \u2014 Restart and verify the DVD drive<\/h4>\n<p>Restart Windows, then open:<\/p>\n<pre><code>Device Manager \u2192 DVD\/CD-ROM drives \u2192 Properties \u2192 General<\/code><\/pre>\n<p>In this case, the error disappeared and Windows reported:<\/p>\n<blockquote><p>This device is working properly.<\/p><\/blockquote>\n<p>The DVD drive was operating with the standard Microsoft driver. No additional driver installation was necessary.<\/p>\n<h3>Final result<\/h3>\n<p>After disabling <code>PxHlpa64.sys<\/code> and removing its DVD <code>LowerFilters<\/code> reference:<\/p>\n<ul>\n<li>Windows 11 booted normally.<\/li>\n<li>Multiple restarts completed successfully.<\/li>\n<li>The DVD drive was recognized without errors.<\/li>\n<li>Obsolete multimedia applications were subsequently uninstalled.<\/li>\n<li>Windows Update ran successfully again.<\/li>\n<\/ul>\n<p>The old <code>PxHlpa64.sys<\/code> file remained on disk, but its startup setting stayed at <code>Start = 4<\/code>. There was no need to delete it manually.<\/p>\n<p><strong>No Windows reinstall was required.<\/strong><\/p>\n<h3>Could this fix help other affected systems?<\/h3>\n<p>If Windows 11 enters an Automatic Repair or <code>SrtTrail.txt<\/code> boot loop after an update, and standard recovery methods fail, checking for the legacy <code>PxHlpa64.sys<\/code> driver may be worthwhile \u2014 particularly on older systems with optical drives or legacy disc-burning software.<\/p>\n<p>The issue is not necessarily specific to Lenovo, and KB5132061 is not confirmed as the trigger in every case. However, the combination of an old boot-start filter driver and a recent Windows update is a useful diagnostic lead.<\/p>\n<p>The key lesson: <strong>before resetting or reinstalling Windows, check whether an obsolete third-party boot driver is preventing startup.<\/strong><\/p>\n<h3>References<\/h3>\n<ul>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/servicing\/os\/windows-11\/2026\/11\/kb5132061-windows-11-24h2-25h2-26h2-security-update\">Microsoft \u2014 Windows 11 November 10, 2026 Security Update (KB5132061)<\/a><\/li>\n<li><a href=\"https:\/\/borncity.com\/blog\/2026\/11\/18\/windows-11-25h2-26h2-boot-schleife-durch-pxhlpa64-sys-nach-nov-2026-update-kb5132061\/\">Born&#8217;s IT and Windows Blog \u2014 Windows 11 boot loops involving PxHlpa64.sys following KB5132061<\/a><\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/windows\/hardware\/drivers\/your-cd-or-dvd-drive-is-not-recognized-by-windows-or-other-programs\">Microsoft Support \u2014 CD\/DVD drive errors and UpperFilters\/LowerFilters<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<h2>Windows 11 Boot Loop After November 2026 Update: Fixing PxHlpa64.sys<\/h2>\n<p><strong>Short version:<\/strong> A Windows 11 computer became stuck in an endless Automatic Repair loop following the November 2026 Windows updates. The problem was traced to an outdated optical-disc driver, <code>PxHlpa64.sys<\/code>, dating from 2013. Disabling the driver restored Windows startup. Removing its obsolete <code>LowerFilters<\/code> reference subsequently restored the DVD drive.<\/p>\n<p>The issue was resolved on a <strong>Lenovo ThinkStation running Windows 11<\/strong>, without reinstalling Windows or losing personal files.<\/p>\n<p>Similar failures have been reported following the November 10, 2026 security update <strong>KB5132061<\/strong>, although the exact update responsible for this particular incident could not be conclusively identified.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6,12],"tags":[],"_links":{"self":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/248"}],"collection":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/comments?post=248"}],"version-history":[{"count":13,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions"}],"predecessor-version":[{"id":266,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions\/266"}],"wp:attachment":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/media?parent=248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/categories?post=248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/tags?post=248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}