Windows 10
A Microsoft operating system that runs on personal computers and tablets.
6,601 questions
UWP app crash immediately after opening with Faulting module name: KERNELBASE.dll Event Log
Samip Dahal
1
Reputation point
Hi all,
I have developed a UWP app and uploaded it to Windows Store. Everything was working perfectly fine until I created a new self-signing certificate after the previous one expired and re-published the new changes to the store. The application after downloading and installing from the store crashes immediately after opening and leaves an event log with the below error in the Windows Event Viewer. The same issue occurs when installing through a side-loading build.
I have tried all methods suggested online(running system scan for corrupted files, register dll, use dll file from another system, etc). I have also uploaded an image showing my windows version. Any help will be appreciated. Thank you.
Faulting application name: XYZWindowsApps.exe, version: 1.0.1.0, time stamp: 0x61e99c28
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1466, time stamp: 0xe01c7650
Exception code: 0xc000027b
Fault offset: 0x000000000010b362
Faulting process id: 0x2d0c
Faulting application start time: 0x01d80e24b18250ad
Faulting application path: C:\Program Files\WindowsApps\NameXYZ.AppName_1.0.13.0_x64__tesn1012p7f1y\XYZWindowsApps.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 07e3f487-1127-4f89-ba1b-1e1cb032168c
Faulting package full name: NameXYZ.AppName_1.0.13.0_x64__tesn1012p7f1y
Faulting package-relative application ID: App
Windows 10
Universal Windows Platform (UWP)
Universal Windows Platform (UWP)
A Microsoft platform for building and publishing apps for Windows desktop devices.
2,522 questions
C#
C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
7,502 questions
{count} votes
-
Reza-Ameri 14,796 Reputation points
2022-01-21T16:03:08.38+00:00 Are you facing this issue with the application you developed?
What programming language did you used?
Are you facing this issue with the application you developed? -> Yes
What programming language did you used? -> C# with Microsoft.NETCore.UniversalWindowsPlatform -Version 6.2.9
Start with a debugger attached: what the is exception and call stack?
But perhaps there is already more information in application event log.
UWP had its special exception, debugging this was not so trvial: Stowed Exception C000027B
But maybe easier when done in a current version of Visual Studio
You will have to do debug and add breaking points and investigate where this problem started?
Locally the application works perfectly fine. I also attached file logging at some specific points in the App() constructor and App.xaml.cs file, but couldn't get any traces there.
It makes sense to check what happens in Release mode when Debug flag is set. It could be some bug in .Net Native.
Sign in to comment
1 answer
Sort by: Most helpful
Hi there,
As it seems you have tried all possible solutions (running system scan for corrupted files, register dll, use DLL file from another system, etc) the only option would be to do an in-place upgrade.
How to perform an In-place Upgrade with Windows 10 Step-by-Step Guide
https://answers.microsoft.com/en-us/windows/forum/all/how-to-perform-an-in-place-upgrade-with-windows-10/7f0b236e-3c6c-4913-9691-c4baa2a6190a
The file KernelBase.dll is a DLL file stored in the system folder of the Windows operating system. It is created automatically during the installation of the Windows operating system. KernelBase.dll is used to launch .exe applications. When it is corrupt, you will get .dll missing or not found error when you start the programs.
--If the reply is helpful, please Upvote and Accept it as an answer--
Hi everone,
Thank you to all who tried to help and share their knowledge regarding this issue. It has been resolved. The underlying issue was due to a third party SDK for some device connectivity I was using with this application, which was generating an internal error and was either unhandled or not getting caught for previous versions of Windows. It has been successfully handled now and is working fine.
Thanks.
Sign in to comment