Hi @JoeA

I am having the same issue reported in the first post of this thread creating Reflect Rescue Media using Windows RE on my 64-bit Windows 10 Pro 22H2 19045.3448 build. Today, I just upgraded to from 8.1.7544 to 8.1.7638 version and tested trying to boot from the Reflect Rescue Media DVD I created from 8.1.7638 version which fails with the same BSOD as shown in the first post of this thread.

I am not interested in the workaround of using Win PE 10.

Any update of when this issue will be fixed?

I noticed that my DVD size after creation from the 8.1.7638 Reflect Home edition was a smaller size of 892 MB used space verses 1.17 GB used on the 8.1.7544 version.

@DanDanz

FYI. Looking at Windows > Settings > Update & Security > View update history, I do not find any installation of the KB5029331 on my PC.

EDIT: Not all users of Reflect test their recreated Rescue Media after an upgrade. This means users can be facing a dire moment scenario to restore their system with no way to use the Reflect Rescue Media they depend on to work.

Greetings -- 

Thanks for posting your issue --- It seem that KB5029331 was the "preview" the regular monthly patch KB5030211 and my guess that KB5030211 would update the same files
that KB5029331 would have updated if it was applied.  Like you I did notice a sharp size reduction when I too created the ISO for reflect 7638. 

@DanDanz posted that he submitted a ticket to support and said he would post their reply, but I have not seen any such post

I did get a reply to a message I sent to @JoeA which he noted that this is a Microsoft issue due to KB5030211

It is not clear to me if reflect support posted this issue to Microsoft  for their comment on the issue,  so  untill there is some resolution to the issue 
only Win PE will work

Hi @fpefpe

Thank you for sharing your update and analysis.

Has Macrium support or a Reflect user tried the September 26, 2023—KB5030300 (OS Build 19045.3516) Preview to see if this resolves the issue?

+x

 

Reflecting Mirror - 27 September 2023 4:18 PM

Hi @fpefpe

Thank you for sharing your update and analysis.

Has Macrium support or a Reflect user tried the September 26, 2023—KB5030300 (OS Build 19045.3516) Preview to see if this resolves the issue?

I posted this issue about KB5029331. on askwoody.com ---  2 replies were to take note of --- 

1)   it is not  recommended to apply "preview" patches

2)  remove KB5029331

So, at this point I am not going to apply KB5030300

and it is not clear to me what issues I could have by uninstalling KB5029331 so I did not attempt to do that

I used to apply Windows OS Preview patches until I got burned by one of them. I can't remember the issue, but I decided to avoid installing the MS Preview patches.

I did notice in the past when I did apply the Preview patch that when I applied the production patch that occurred on Microsoft's patch Tuesday (second Tuesday of every month), went a lot faster for the production patch. Likely just the production patch delta being applied from the more time consuming Preview patch.

I have applied September 26, 2023—KB5030310 (OS Build 22621.2361) Preview to my Windows 11 Laptop (guinea pig) system -- and like the earlier preview patch 2023-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5030219) -- no problems were ever noted ON WINDOWS 11.

On the Windows 10 system that had the major problems that required restoring to recover it has been updated without drama to the next Patch Tuesday update -- September 12, 2023—KB5030211 (OS Build 19045.3448), and I have suspended Updates for 7 days -- I HAVE NOT INSTALLED September 26, 2023—KB5030300 (OS Build 19045.3516) Preview on it.  I believe it will be applied when I resume updates and I have ensured adequate backups have been taken. . 

I have never seen any indication (or acknowledgement of my Feedback report) from Microsoft that there has been either a fix for KB5020219, or inclusion of its fixes in Patch Tuesday updates.  But now I'm paranoid, hence the suspension of Windows Updates on the Win 10 system(s)

AFAIK, the support folks were not able to reproduce the problem.   Because other users have reported similar problems after applying KB5030219 with wildly varying experiences and symptoms (including one whose problems appeared on RM builds with WinPE10 but was able to successfully rebuild RM with WinRE 10, the exact opposite of my experience), I don't believe the problem is in Reflect, but rather in Windows patches.  Therefore I concur with their decision to close my original ticket.  We don't know the exact cause or the exact environment that produced the problem.


L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7638+ on Windows 11 Home 23H2 22631.2715+  

+x

 

Reflecting Mirror - 27 September 2023 4:39 PM

I did notice in the past when I did apply the Preview patch that when I applied the production patch that occurred on Microsoft's patch Tuesday (second Tuesday of every month), went a lot faster for the production patch. Likely just the production patch delta being applied from the more time consuming Preview patch.

@Reflecting Mirror I wonder if the difference is in the system restore point they could create when installing preview patches.  I don't depend on those to uninstall patches anyway, preferring to use Reflect backups instead. 


L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7638+ on Windows 11 Home 23H2 22631.2715+  

+x

 

Dan Danz - 27 September 2023 7:25 PM

I have applied September 26, 2023—KB5030310 (OS Build 22621.2361) Preview to my Windows 11 Laptop (guinea pig) system -- and like the earlier preview patch 2023-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5030219) -- no problems were ever noted ON WINDOWS 11.

On the Windows 10 system that had the major problems that required restoring to recover it has been updated without drama to the next Patch Tuesday update -- September 12, 2023—KB5030211 (OS Build 19045.3448), and I have suspended Updates for 7 days -- I HAVE NOT INSTALLED September 26, 2023—KB5030300 (OS Build 19045.3516) Preview on it.  I believe it will be applied when I resume updates and I have ensured adequate backups have been taken. . 

I have never seen any indication (or acknowledgement of my Feedback report) from Microsoft that there has been either a fix for KB5020219, or inclusion of its fixes in Patch Tuesday updates.  But now I'm paranoid, hence the suspension of Windows Updates on the Win 10 system(s)

AFAIK, the support folks were not able to reproduce the problem.   Because other users have reported similar problems after applying KB5030219 with wildly varying experiences and symptoms (including one whose problems appeared on RM builds with WinPE10 but was able to successfully rebuild RM with WinRE 10, the exact opposite of my experience), I don't believe the problem is in Reflect, but rather in Windows patches.  Therefore I concur with their decision to close my original ticket.  We don't know the exact cause or the exact environment that produced the problem.

Well, now I can report that the latest PREVIEW update KB5030300 for Windows 10 repeats the same problem of not being able to create a working Rescue Media using WinRE 10. The error message about a missing NTOSKERNEL.exe is the same when you boot the RM, including the error code 0xC000A004.

I tried uninstalling KB5030300 once, and it worked - I was able to create the WRBM version and the USB Flash version of Rescue Media.
Then, just to be sure, I let Windows Update install the PREVIEW again, and it failed in the same way.   This time, I tried restoring the Recovery Partition from the backup rather than C:\ and Recovery Volumes.   Didn't fix it.
So I restored all paritions on the System Disk from a backup created the same day at 00:30.  All traces of the problem are gone.   And I'm leaving it that way -- with the preview patch now waiting for approval to install it from Windows Update.   I haven't looked, but I'm sure it will be pending as an optional patch on my 2 other Windows 10 systems. I'll have to be alert for it showing up as a non-preview update.   @JoeA Please advise the team that worked on the earlier ticket.  I'm not going to reopen it or a new ticket. I'd love to know what it is about this patch that causes bad RM builds by Reflect.


L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7638+ on Windows 11 Home 23H2 22631.2715+  

thanks for the  update 

Just FYI I have that update, tried a WinRE in Windows 10 and booted fine.  I didn't try a WinPE however.