Kernelbase error when starting application which worked fine about a year back...

Question

Rollback is not an option, there is no point in trying since it has been a year that the application was used (game). When installing at first go, also tested now on another system with same version of Windows 10, the game worked fine. Now I get a dual error that so far I have not been able to fix.
Tried DISM with several options and followups, SFC finds no errors and trying the fixer for .Net installation found no error that it could fix.
Drivers for all installed hardware are up to date. DirectX Diag finds no errors.
I am at a loss how to get this fixed (short of reinstalling Windows which I still hope to avoid...).

This is the error for the application:
Faulting application name: Launcher.exe_Homeworld:Remastered launcher, version: 1.0.0.0, time stamp: 0x5759dce3

Faulting module name: KERNELBASE.dll, version: 10.0.19041.1466, time stamp: 0xc79f51a9

Exception code: 0xe0434352

Fault offset: 0x0012b662

Faulting process id: 0xcd8

Faulting application start time: 0x01d808cb0819e3be

Faulting application path: E:\Games\SteamSecondLib\steamapps\common\Homeworld\HWLauncher\Launcher.exe

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

Report Id: b8c88a02-a139-4907-93fb-28ea11b8152a

Faulting package full name: 

Faulting package-relative application ID: 

In tandem with the application error (timestamp too closeto the application error):
Application: Launcher.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArithmeticException

Exception Info: System.OverflowException

   at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()

   at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(System.Windows.Media.Imaging.BitmapSource, System.Windows.Media.ColorContext, System.Windows.Media.ColorContext, System.Windows.Media.PixelFormat)

   at System.Windows.Media.Imaging.BitmapSource.CreateCachedBitmap(System.Windows.Media.Imaging.BitmapFrame, System.Windows.Media.Imaging.BitmapSourceSafeMILHandle, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Windows.Media.Imaging.BitmapPalette)

   at System.Windows.Media.Imaging.BitmapFrameDecode.FinalizeCreation()

   at System.Windows.Media.Imaging.BitmapFrameDecode..ctor(Int32, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Windows.Media.Imaging.BitmapDecoder)

   at System.Windows.Media.Imaging.BitmapDecoder.SetupFrames(System.Windows.Media.Imaging.BitmapDecoder, System.Collections.ObjectModel.ReadOnlyCollection`1<System.Windows.Media.Imaging.BitmapFrame>)

   at System.Windows.Media.Imaging.BitmapDecoder.get_Frames()

   at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(System.Uri, System.Uri, System.IO.Stream, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Net.Cache.RequestCachePolicy)

   at System.Windows.Media.ImageSourceConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)

   at System.Windows.Baml2006.TypeConverterMarkupExtension.ProvideValue(System.IServiceProvider)

   at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(System.Windows.Markup.MarkupExtension, System.IServiceProvider)

Exception Info: System.Windows.Markup.XamlParseException

   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)

   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)

   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)

   at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)

   at System.Windows.Application.LoadComponent(System.Uri, Boolean)

   at System.Windows.Application.DoStartup()

   at System.Windows.Application.<.ctor>b__1_0(System.Object)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.DispatcherOperation.InvokeImpl()

   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)

   at System.Windows.Threading.DispatcherOperation.Invoke()

   at System.Windows.Threading.Dispatcher.ProcessQueue()

   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)

   at System.Windows.Application.RunDispatcher(System.Object)

   at System.Windows.Application.RunInternal(System.Windows.Window)

   at System.Windows.Application.Run(System.Windows.Window)

   at Launcher.App.Main()

(Forgot device and OS info, sorry.)

Device name R6-I7
Processor Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz 3.40 GHz
Installed RAM 16,0 GB
Device ID
Product ID
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Video is on a Gigabyte RTX 2060 Super with 8GB of VRAM (plenty above spec and then some).

Edition Windows 10 Pro
Version 21H2
Installed on ‎11/‎10/‎2020
OS build 19044.1466
Experience Windows Feature Experience Pack 120.2212.3920.0

Answer 1

Thank you Greg for your response.

System restore will not work as there is no point to restore to. It was turned off.

I will go over the given tips towards restoring my system though most of them I am already familiar with and so far have not helped in fixing it. The errors given remain the same leading me to think that the file kernelbase.dll is indeed the problem in combination with a conflict in the .Net installs as there are 5 o versions in my system listing, also six versions of VCRedist.
edit: The game is installed using Steam, uninstalls and re-installs have not solved the issue.

Note I've kept this rig running for nearly ten years now, of which the last few years in Windows 10. I must say that installing 10 was a breeze compared to the other versions. In troubleshooting this problem I've come across a post on this forum where the repair/reinstall failed which led me to post here in hopes of not having to resolve to that for fear of having to restart with a wiped system. That said, thank you again for the post I will update as and when warranted here.

David

Answer 2

Hi Hazel. I'm Greg, 10 years awarded Windows MVP, specializing in Installation, Performance, Troubleshooting and Activation, here to help you.

It doesn't matter when the game was played last, System Restore is still your first line of defense because it can get back before an Update or something else was installed that might have caused this. It works like a time machine, so try it now working backwards to see if you can find a point where the game still works:

https://www.windowscentral.com/how-use-system-r...

Even if you've already tried one of these steps, please do them over in sequence:

1. Check for game Updates in MS Store Hub (three dots at top right of Store app) > Downloads & Updates.
2. Run the MS Store apps troubleshooter at Windows Settings > Update & Security > Troubleshoot > Additional Troubleshooters > Windows Store Apps.
3. Try to Reset or Repair the game in Windows Settings > Apps > Apps & Features > [Name of game] > Advanced Options > Reset or Repair. Restart PC.
4. If that's not enough then uninstall the game from the same place, restart PC, reinstall the game from MS Store Hub (three dots at top right of Store app) > My Library.
5. If the above steps don't help then go over this checklist to make sure the install is set up correctly, optimized for best performance, and any needed repairs get done:

http://answers.microsoft.com/en-us/windows/wiki...

Start with Step 4 to turn off Startup freeloaders which can conflict and cause issues, then Step 7 to check for infection the most thorough way, then step 10 to check for damaged System Files, and also Step 16 to test a new Local Admin account. Then continue with the other steps to go over your install most thoroughly.

6. Update your drivers and BIOS/UEFI firmware from PC or motherboard maker's Support Downloads web page, using the full model number, Serial Number or Dell Service Tag on sticker. Compare the latest drivers available for download with the ones presently installed in Device Manager reached by right clicking the Start button. Make sure you have the latest BIOS or UEFI firmware, Chipset, Display (Video), Sound, USB3, Bluetooth, Network and all other drivers, or else download and install the latest now.

Updating drivers from the Device Manager or Windows Update is rarely enough. The most basic thing we need to learn to maintain a PC is keep the latest manufacturer's drivers installed from their Support Downloads web page.

7. If nothing else works then do a Repair Install, by installing Media Creation Tool, open tool and choose to Upgrade Now. This reinstalls Windows while keeping files, programs and most settings in place, is the most stable method to advance to the latest version, and solves most problems. https://www.microsoft.com/en-US/software-downlo...

I hope this helps. Feel free to ask back any questions and keep me posted. If you'll wait to rate whether my post resolved your problem, I will keep working with you until it's resolved.

______________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.