Hi Everyone!
This is more of a Solution post, rather than a technical question or issue, as I've already solved this an hour ago.
Yesterday, during a power outage, my workstation was affected. After booting up once power was restored, one of my applications (Logitech G Hub) was stuck on a loop where the logo is just spinning around trying to load in, causing my mouse (Logitech G600) not able to load in any of its configurations, which lead to a very low DPI, left/right mouse buttons were not working correctly, it just stressed me out.
After searching around to try to identify the issue, I ended up on the Event Viewer, which provided the following message:
Faulting application name: lghub_agent.exe, version: 2024.7.1167.0, time stamp: 0x66e075d9
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe
Faulting process id: 0x0x5E4C
Faulting application start time: 0x0x1DB0C938BAE799B
Faulting application path: C:\Program Files\LGHUB\lghub_agent.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 5d433658-96ba-4594-9108-d737b5fc7f32
Faulting package full name:
Faulting package-relative application ID:
Attempting to do anything was futile as this happened around 4AM and I was already tired, searching around the Community Forum & external sites I couldn't find anything so I just shutdown and went to sleep, today I started fidgeting around with this once again until I have finally fixed the issue.
But, before providing the fix, here's what I found during my research:
In one, of the many posts, I found, it was mentioned to un-register/register the 'ucrtbase.dll', this should've been possible by going into Safe Mode and using CMD (Admin) to un-register the dll, delete it, replace it with a freshly downloaded version of it and registering it back with CMD.
This turned out to be impossible, due to the fact that 'ucrtbase.dll' does not come with 'DLLREGISTERSERVER' included in its code, this makes it impossible even for a Technician like myself to accomplish it. (I found out about this information on the following post: Problem registering a '.dll' with Command Prompt - Microsoft Community)
Many others have mentioned to use DISM command tool, which I of course attempted to use, it did find errors, supposedly fixed them, but didn't really (who could've guessed right?).
Either ways. After a more thorough search across the web, I found out that 'ucrtbase.dll' has actually been in existence since 2013, some people have mentioned have ran into this issue on that OS, with no solution to be found, other than re-imaging/fresh Windows install, which being honest isn't acceptable, due to the time it would take to reinstall and reconfigure everything to it's past state. (using a Restore Point would also be the solution, but that wouldn't actually solve the issue, right? If the problem would present itself again I'd have no response to my self on how to actually fix it, sorry I digress)
Continuing on, the post mentions that; Universal CRT ('ucrtbase.dll') has formed part of Windows OS since W10/WS-2k16. This post also mentions that the DLL is part of Visual Studio .Net, which lead me to assume this came as part of Microsoft's C++ Redistributables, lo and behold I was correct.
[Source: Universal CRT deployment | Microsoft Learn]
So, what is the Solution?:
1.- Open Windows Settings
2.- Navigate to Apps > Installed Apps
3.- Locate the following:
• Microsoft Visual C++ 20XX Redistributable - x64
• Microsoft Visual C++ 20XX Redistributable - x86
4.- Uninstall
5.- Download & Install the latest C++ Redistributables from the Official Website: Latest supported Visual C++ Redistributable downloads | Microsoft Learn
6.- Reboot
I'm not entirely sure if all Redistributables are at fault or only the 2015-2022. I decided to uninstall all of these & reinstall them for an easier transition. Takes around 5-10 minutes at most to perform this.
Lo and behold, this solved my whole ordeal of dealing with a nuissance that affected one of my peripherals at the end of the day.
But I am also sure, from all the posts I've read, that this issue is present on way more applications, from end users to developers.
I hope this information helps anyone out there & avoid consuming more time than required.