{"id":10873,"date":"2019-08-24T00:01:00","date_gmt":"2019-08-23T22:01:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10873"},"modified":"2021-07-23T16:07:14","modified_gmt":"2021-07-23T14:07:14","slug":"windows-7-sp1-update-kb4512506-causes-error-0xc0000225","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/08\/24\/windows-7-sp1-update-kb4512506-causes-error-0xc0000225\/","title":{"rendered":"Windows 7 SP1: Update KB4512506 causes error 0xc0000225"},"content":{"rendered":"

\"win7\" [German<\/a>]The monthly KB4512506 Security Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 is experiencing issues. Some systems run into boot problems during installation. The machines refuse to start with error code 0xc0000225.<\/p>\n

<\/p>\n

The error description<\/h2>\n

\"\"Austrian blog reader Friedrich S., who runs an IT support company, contacted me by e-mail. He describes the error as follows::<\/p>\n

\n

after installation of 2019-08 – Monthly Security Quality Rollup for Windows 7 for x64-based Systems (KB4512506), Windows 7 no longer starts on some PCs. The error message:<\/p>\n

Status: 0xc0000225
Info: The boot selection failed because a required device is inaccessible. <\/p>\n<\/blockquote>\n

\"Windows <\/p>\n

The blog reader writes that the safe mode of Windows 7 no longer works either. With a Linux USB stick he can start the systems and also access the partitions\/data. <\/p>\n

The blog reader is not alone; after I wrote the article Windows 7: SHA-2-Klippen am August-Patchday<\/a> for German magazine heise, some readers left comments like<\/a> the one, I've translated here: <\/p>\n

\n

KB4512506 causes a blackscreen with error 0xc0000225 (Win7 x64)<\/p>\n

KB4474419 and KB4490628 are installed, but as soon as the 2019-08 monthly security quality rollup is installed, the Windows Boot Manager stalls with status 0xc0000225.  <\/p>\n

What I found so far was the suggestion to restore the winload.efi and winload.exe in system32 from an intact system, but I haven't tried it yet. <\/p>\n

Has anyone else been able to observe this?<\/p>\n<\/blockquote>\n

In the thread other users confirm this problem. Krebs on Security also has this user comment<\/a>. Askwoody also has this forum entry<\/a>, and Spiceworks also confirms the bug<\/a>.  <\/p>\n

Repair attempts of the user<\/h2>\n

The affected person then tried to boot the systems via Windows 7 DVD and get into Windows PE via the computer repair options. But he had no success there. After the start with the Windows 7 DVD he received this message during system restore <\/p>\n

\n

This version of the System Restore Options is not compatible with the version of Windows you are repairing. Use a disk that is compatible with this version of Windows. <\/p>\n<\/blockquote>\n

FYI: Windows 7 x64 SP1 is installed on the computer, Windows 7 x64 SP1 is also installed on the DVD. If you use the Windows repair disk for starting, an error is found in the Windows boot manager. <\/p>\n

\n

Reparaturdetails: Die folgende Startoption wird repariert:
Name: Windows Boot Manager
ID: 9DEA862C-5CDD-4E70-ACC1-F328344D4795 <\/p>\n<\/blockquote>\n

\"Reparatur  <\/p>\n

After the repair has been carried out, the starting problem persists. The affected user writes to this: <\/p>\n

\n

We already have 5 systems where the problem occurs, 3 systems use a Samsung 860 Pro SSD, 2 systems have an HDD (Seagate\/WD) built in. <\/p>\n<\/blockquote>\n

and asks if others are affected and if there are any solutions. I had answered the question about the afflictions of other users in the text above with links to other sources.  <\/p>\n

Troubleshooting, some approaches<\/h2>\n

Ad-hoc I guess that the boot manager will be patched by the SHA-2 update in Windows 7. I had already published the blog post Windows h\u00e4ngt mit Boot-Fehler 0xC0000225<\/a> in December 2015, which deals with the error image. There was a tip to repair the UEFI files. But I am skeptical that it will help.<\/p>\n

Patch KB3133977 is missing?<\/h3>\n

While writing the blog post something rang with me. A few days ago I published the article Windows 7: Reinstallation causes boot error 0xc0000428<\/a>. Microsoft states that in certain situations a missing Bitlocker patch KB3133977 causes the stop error 0xc0000428. <\/p>\n

\n

Here it is recommended to read the support article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS<\/a>. Microsoft has added three entries to the August 17, 2019 article. The entries at the end of the article address issues related to the SHA-2 upgrade in Windows 7 SP1 and Windows Server 2008 R2.  <\/p>\n<\/blockquote>\n

At heise I had published the article Windows 7: SHA-2-Klippen am August-Patchday<\/a>. There I mentioned the missing Bitlocker update KB3133977 may causes boot issues. Then I got an interesting user hint in the comment<\/a> thread to my article. <\/p>\n

\n

It also bricked some of my computers. Fortunately they could be retrieved via restore points. After installing KB3133977 KB4512506 could be installed without any problems. <\/p>\n

Be careful with the patch KB3133977 in connection with ASUS boards and Secure Boot. Be sure to read the KB article!<\/p>\n<\/blockquote>\n

So the Bitlocker patch KB3133977 can solve the problem with the boot problems here as well. I therefore guess that the Windows 7 boot manager can no longer read the signatures without update KB3133977 due to the SHA-2 error and refuses to boot. <\/p>\n

\n

Microsoft wrote something about the ASUS board problem in KB article 3133977<\/a> that the patch on ASUS board prevents booting. ASUS has published this support article<\/a>.    <\/p>\n<\/blockquote>\n

Perhaps the above information will help. If so, just leave a comment – thank you. <\/p>\n","protected":false},"excerpt":{"rendered":"

[German]The monthly KB4512506 Security Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 is experiencing issues. Some systems run into boot problems during installation. The machines refuse to start with error code 0xc0000225.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,2],"tags":[2084,47,2058,195,17],"class_list":["post-10873","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-error-0xc0000225","tag-issue","tag-kb4512506","tag-update","tag-windows-7"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=10873"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10873\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=10873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=10873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=10873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}