Faulting module name: KERNELBASE.dll, version: 10.0.19041.3992, Faulting module name: CONCRT140_APP.dll

It's got to be related to legacy CPUs. Mine is Core 2 quad Q8300.

Yes, it's readily apparent that no Intel Core 2 CPUs can run the latest version of these apps. I don't know precisely what Microsoft has done, but since the only difference is CPUs being used, the CPUs that work must logically support something that Intel Core 2 CPUs don't (or have some characteristic that Intel Core 2 CPUs don't).

Regardless, this situation is ridiculous because many of these apps offer minimal functionality. Let's say SSE4.2 is now required, speculatively speaking. Is that really necessary for the Feedback Hub application? Please, Microsoft.

Your 4th gen i5 CPU supports SSE4.2, for what it's worth.

Given they're both Intel Core 2 processors, the findings appear to be relatively consistent. It's not as though people are reporting the same problem while using significantly newer generation CPUs and running these apps, which are updated in the background via the Microsoft Store.

Windows updates are independent of Microsoft Store app updates, which update in the background daily.

If you wish to disable Microsoft Store apps from updating, open the Microsoft Store application, click on your avatar in the upper right, select settings, and toggle off "App Updates" (slider).

You can view Microsoft Store app modification history, by running the Microsoft Store app and then selecting "Library" on the bottom left. All of the affected apps are updated via the Microsoft Store, including Microsoft Photos.

You can view installed app versions, by clicking Start, navigating to the app in your app list, right-clicking on it, selecting "More", and selecting "app settings". A new window will appear showing "Version". I find it's difficult to discuss problems when app versions aren't mentioned.

For Windows version, press the Windows logo key + R, type "winver" in the box, and then select "OK".

Windows 10 Pro 64 bit edition, Version 22H2 (OS Build 19045.3930), with no pending Windows updates, exhibits this issue on a PC here, using an Intel Core 2 Quad core CPU, using the following app versions (information provided by Event Viewer):

Photos 2024.11010.1002.0

Faulting application name: PhotosApp.exe, version: 0.0.0.0, time stamp: 0x659f3d43

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x4494

Faulting application start time: 0x01da508377bd06a2

Faulting application path: C:\Program Files\WindowsApps\Microsoft.Windows.Photos_2024.11010.10002.0_x64__8wekyb3d8bbwe\PhotosApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: a7f21100-823a-43e9-a8e2-396aa00bf863

Faulting package full name: Microsoft.Windows.Photos_2024.11010.10002.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Calculator 11.2311.0.0

Faulting application name: CalculatorApp.exe, version: 11.2311.0.0, time stamp: 0x65984a23

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x3b34

Faulting application start time: 0x01da5082eae764bc

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_11.2311.0.0_x64__8wekyb3d8bbwe\CalculatorApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: a236ddf8-8e19-4900-b992-41e0f3786449

Faulting package full name: Microsoft.WindowsCalculator_11.2311.0.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Mail and Calendar 16005.14326.21786.0

Faulting application name: HxCalendarAppImm.exe, version: 16.0.14326.21786, time stamp: 0x6597575c

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x105c

Faulting application start time: 0x01da50842d5e6f54

Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_16005.14326.21786.0_x64__8wekyb3d8bbwe\HxCalendarAppImm.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: 166514ed-6118-40b8-a3e3-a6429fea7f78

Faulting package full name: microsoft.windowscommunicationsapps_16005.14326.21786.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: microsoft.windowslive.calendar

Films & TV 10.22091.10051.0

Faulting application name: Video.UI.exe, version: 10.22091.1005.0, time stamp: 0x6530e1eb

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x2760

Faulting application start time: 0x01da5084425fe2ab

Faulting application path: C:\Program Files\WindowsApps\Microsoft.ZuneVideo_10.22091.10051.0_x64__8wekyb3d8bbwe\Video.UI.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: f0c09420-d1d5-4ed4-b0ae-c313807baacb

Faulting package full name: Microsoft.ZuneVideo_10.22091.10051.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: Microsoft.ZuneVideo

Paint 3D 6.2310.24037.0

Faulting application name: PaintStudio.View.exe, version: 0.0.0.0, time stamp: 0x65387a54

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x48d8

Faulting application start time: 0x01da508453accc7b

Faulting application path: C:\Program Files\WindowsApps\Microsoft.MSPaint_6.2310.24037.0_x64__8wekyb3d8bbwe\PaintStudio.View.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: f7513880-be05-426e-acb5-a2156b2c1763

Faulting package full name: Microsoft.MSPaint_6.2310.24037.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: Microsoft.MSPaint

Feedback Hub 1.2309.12711.0

Faulting application name: PilotshubApp.exe, version: 1.2309.2309.28001, time stamp: 0x65152eaf

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979

Exception code: 0x00001007

Fault offset: 0x000000000012db22

Faulting process ID: 0x5294

Faulting application start time: 0x01da50840995bdac

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsFeedbackHub_1.2309.12711.0_x64__8wekyb3d8bbwe\PilotshubApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 97a1d38d-96f0-447e-ab79-abe02d35564e

Faulting package full name: Microsoft.WindowsFeedbackHub_1.2309.12711.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Voice Recorder 10.2103.28.0

Faulting application name: SoundRec.exe, version: 10.2103.28.0, time stamp: 0x60622fa3

Faulting module name: CONCRT140_APP.dll, version: 14.39.33321.0, time stamp: 0xd07ef3fe

Exception code: 0xc000001d

Fault offset: 0x00000000000166f4

Faulting process ID: 0x35a4

Faulting application start time: 0x01da5084b44889af

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsSoundRecorder_10.2103.28.0_x64__8wekyb3d8bbwe\SoundRec.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.33321.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll

Report ID: 7d641597-feeb-4408-a5d0-134dbbde1406

Faulting package full name: Microsoft.WindowsSoundRecorder_10.2103.28.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Windows upgrade (otherwise known as in place reinstall) didn't fix the issue.

DISM /Online /Cleanup-Image /ScanHealth **** didn't help.

sfc /scannow didn't find anything wrong.

Uninstalling and reinstalling apps didn't fix anything.

Repairing apps didn't fix anything.

Resetting apps didn't fix anything.

Windows Store Apps troublesooter didn't fix anything,

Using powershell to reinstall/obtain, and register packages didn't fix anything.

Deleting and reinstalling the Microsoft Store app didn't fix anything, of course.

Creating a new local user account and signing into it doesn't change anything.

Disabling antivirus and my firewall, of course, doesn't fix anything.

Affected account is an Administrator account.

If anyone cares, there's another thread discussing the same problem over here: https://answers.microsoft.com/en-us/windows/forum/all/microsoft-photos-file-system-error-2147219196/3bf0b7d0-4390-46f2-b948-a1e05d726e73

I have the same problem. It came with the last automatic app update.

Actions taken: Resetting the app, uninstalling and reinstalling. Result: The app crash during start and ask for debugging via vsc or vs2022.

System: Windows 10 Pro x64, Version: 22H2, Build: 19045.3930

Error via Visual Studio Debugger:

Ausnahmefehler bei 0x00007FF83AFBDB22 (KernelBase.dll) in CalculatorApp.exe: 0x00001007

Debug information:

> KernelBase.dll!00007ff83afbdb22() Unbekannt
SharedLibrary.dll!00007fff8abd38de() Unbekannt
SharedLibrary.dll!00007fff8abd3829() Unbekannt
SharedLibrary.dll!00007fff8ad7b94c() Unbekannt
mrt100_app.dll!00007fff8caea472() Unbekannt
mrt100_app.dll!00007fff8caeeb81() Unbekannt
mrt100_app.dll!00007fff8caf59a7() Unbekannt
ntdll.dll!00007ff83d4523af() Unbekannt
ntdll.dll!00007ff83d4014b4() Unbekannt
ntdll.dll!00007ff83d450ebe() Unbekannt
concrt140_app.dll!00007ff81a3b66f4() Unbekannt
concrt140_app.dll!00007ff81a3b60a4() Unbekannt
concrt140_app.dll!00007ff81a3b58f7() Unbekannt
concrt140_app.dll!00007ff81a3b5e39() Unbekannt
concrt140_app.dll!00007ff81a3bc4c2() Unbekannt
concrt140_app.dll!00007ff81a3bbd30() Unbekannt
concrt140_app.dll!00007ff81a3bb17f() Unbekannt
concrt140_app.dll!00007ff81a3b477a() Unbekannt
CalcViewModel.dll!00007fff8ee5fd57() Unbekannt
CalcViewModel.dll!00007fff8ee42ba9() Unbekannt
CalcViewModel.dll!00007fff8ee42850() Unbekannt
CalculatorApp.dll!00007fff88e35d15() Unbekannt
CalculatorApp.dll!00007fff88e36448() Unbekannt
CalculatorApp.dll!00007fff89004846() Unbekannt
CalculatorApp.dll!00007fff8905ea08() Unbekannt
CalculatorApp.dll!00007fff8905e5f9() Unbekannt
CalculatorApp.dll!00007fff8900e98b() Unbekannt
CalculatorApp.dll!00007fff88e4a2df() Unbekannt
CalculatorApp.dll!00007fff88f27e0a() Unbekannt
Windows.UI.Xaml.dll!00007ff82b7d27d3() Unbekannt
Windows.UI.Xaml.dll!00007ff82b7d25a1() Unbekannt
Windows.UI.Xaml.dll!00007ff82b6983fb() Unbekannt
twinapi.appcore.dll!00007ff833d9fe96() Unbekannt
twinapi.appcore.dll!00007ff833d85e0d() Unbekannt
rpcrt4.dll!00007ff83cc6b583() Unbekannt
rpcrt4.dll!00007ff83ccce77b() Unbekannt
rpcrt4.dll!00007ff83cc0d479() Unbekannt
combase.dll!00007ff83c595f6c() Unbekannt
rpcrt4.dll!00007ff83cc4a77b() Unbekannt
combase.dll!00007ff83c56bae3() Unbekannt
combase.dll!00007ff83c56b86e() Unbekannt
combase.dll!00007ff83c59aaf6() Unbekannt
combase.dll!00007ff83c511283() Unbekannt
combase.dll!00007ff83c59dce8() Unbekannt
combase.dll!00007ff83c505036() Unbekannt
combase.dll!00007ff83c563174() Unbekannt
combase.dll!00007ff83c562ed2() Unbekannt
combase.dll!00007ff83c565f0d() Unbekannt
combase.dll!00007ff83c5666e4() Unbekannt
combase.dll!00007ff83c566100() Unbekannt
Windows.UI.dll!00007ff82f40ecf9() Unbekannt
Windows.UI.dll!00007ff82f40eb97() Unbekannt
twinapi.appcore.dll!00007ff833d7e54a() Unbekannt
SHCore.dll!00007ff83d1bbf69() Unbekannt
kernel32.dll!00007ff83d0d7344() Unbekannt
ntdll.dll!00007ff83d4026b1() Unbekannt

I have the exact same problem as described above by AR and others in this forum after the 2024-01 Cumulative Update for Windows 10 Version 22H2 for x64-Based Systems (KB5034122) was installed on January 10, 2024.

I have performed all the same steps as AR without success, all apps open then close immediately and reports errors in the Windows Application Log.

I did a system restore to a restore point prior to this update and the apps worked. Once this update was installed by Windows update all these apps experienced the same problem as before, open for a second or two then immediately close and report these errors in the Windows Application Log.

I also enabled the administrator account, and the problem persists there as well.

There must be a problem with KB5034122!? Will Microsoft realize this and fix it in the next Tuesday updates in February?