Category: Random Fix

Check Computer\HKEY_USERS.DEFAULT\Network for mapped drive letters.

I had disconnected network drives that would not disconnect or delete. This must be an obscure issue as I ALL data I found on the Internet did not mention this place in the registry not once. I had to use a tool from Nirsoft to do a scan of the registry of the UNC. It found this obscure registry path. I deleted the drive letters from this path and it fixed the problem.

I ran into a very obscure almost malwareish type problem with Corsair’s iCue software. Even their own support could not figure out what was causing my computer to shut itself down upon starting icue.exe.

I noticed my computer randomly turning off one day.

I went into Event Viewer and started looking at the System logs. I saw an event that was caused by icue.exe to shut down my computer.

I started investigating the issue more and found that upon starting icue.exe, iCue would open, and then briefly, there’d be a warning message about a sensor over its threshold and immediately my computer would start the shutdown process.

In order to have a normal working computer I would have to log in, open Task Manager, go to Details, search for icue.exe and then kill the icue.exe process before it could sense a false reading of the Corsair QX120 sensor #3.

I had a feeling that there was a configuration file within one of the various iCue folders, but I didn’t know which one. There were many and I didn’t have time to scour through each and every folder looking for the right one. That was, until it pissed me off so much that Corsair’s support couldn’t even figure out what the problem or where the file was.

They continued to insist that if I just did a clean install of iCue that this problem would magically go away. They were wrong. Even after doing a clean install of iCue software, the problem returns immediately. I’m not even sure how the sensor is enabled with a clean install of the iCue software.

In any case, if you run into this issue and you’re seeing a piece of malware like icue.exe shutting down your computer due to a false reading of a sensor from one of the QX series fans, you want to go to %appdata%, Corsair, CUE5, profiles, open up the larger config file, mine was around 315KB, do a search for the text “Emergency Shutdown.”

Under the Emergency Shutdown entry you will see the shutdownPCEnabled option, as well as the shutdown PCTemperature option.

I changed the shutdownPCEnabled to false, and the shutdownPCTemperature to 150 because I KNEW it was a false reading. BEFORE YOU DO THIS, MAKE SURE YOUR COMPUTER IS NOT REALLY OVERHEATING! IF YOUR COMPUTER IS ACTUALLY OVERHEATING THEN ICUE IS DOING ITS JOB OF SAVING YOUR COMPUTER! READ YOUR TEMPS VIA HWINFO32 OR OTHER VARIOUS PIECES OF SOFTWARE TO ENSURE YOUR COMPUTER IS NOT OVERHEATING. I AM NOT RESPONSIBLE IF YOU DISABLE THIS AND YOUR COMPUTER OVERHEATS AND CAUSES ANY ISSUES!

If you run into this error, this is what worked for me. I had to install two Payroll updates by going to Employees, Get Payroll Updates, and installing whatever was available.

I didn’t find much with my Google-Fu, but I found another issue related to outlook.com accounts and put two and two together to fix my issue.

If you run into a problem with a Microsoft 365 Exchange Online account trying to access shared calendars in OWA, but the calendars appear and then disappear – as well as you can’t see the Shared calendars option under OWA (outlook.office.com), Settings, Calendar (there should be Shared calendars here) and OR if you do have Shared calendars as an option, but when you click on it it says unable to load these settings – check the Accounts section under the OWA, Settings, Calendar section. There might be a Microsoft account, which will be a non-work/school account, aka outlook.com account, or an older email address that is probably the same as your work/school account. Remove it from the Account section.

Second, I highly recommend changing the Microsoft account’s sign-in username from [email protected], which is probably your Microsoft 365 work/school username, to [email protected]. You can do this via live.com by logging in to your Microsoft account (non-work/school account) and updating the settings there.

I have been trying to transfer file shares from a Server 2012 Essentials to a Server 2022 server.

I had success two days ago using the same exact set up and Storage Migration Service.

I tried it on a second client and continued to run into problems where it was stuck at the transfer portion and all it said was loading….

I went back to the first server I migrated the other day and I saw there was an update for the Storage Migration Service extension in Windows Admin Center.

I noticed the first server was now stuck at loading.

I didn’t think anything of it as it sometimes happens. You would think Microsoft would test their products and updates – they really don’t.

I finally figured out how to uninstall the WAC extension. You have to turn off automatic updates before you’ll see the option to uninstall an extension.

I reinstalled version 2.44.0 which was the default that came with this Windows Admin Center install package.

As soon as I downgraded the Storage Migration Service package, IT WORKS!

Everything I could find, which wasn’t much, ended up in “update the extension” and that fixed the problem.

I hope this helps someone from pulling their hair out.

I have been trying to figure out why QuickBooks Premier Pro 2022 will not install on Windows Server Essentials 2016.

It gets a quarter of the way in and then throws an error 1603.

I’ve searched high and low and HATE Google results. Nothing but handpicked garbage content farm webpages that do not help at all. I miss you could find an obscure blog on the first or second page with a fix right there. Instead, you get this ad-filled almost AI created gibberish with nothing but rehashed “fixes” from every other website that, again, is filled with nothing but ads.

I’ve tried uninstalling the C++, .Net Framework, etc. to no avail.

I just downloaded a trial of QuickBooks Enterprise 2023 and it installed with NO PROBLEMS.

I stood up a Server Essentials 2016 virtual machine and was able to install QuickBooks Premier 2022 OK with no problem.

However, I came across at least three other people who have had a problem with trying to install QuickBooks Premier 2022 onto either Windows 10 or a server operating system.

If you came across this and fixed it, please comment below. I’ll do the same if I find a fix. I know it will make a lot of people happy.

An interesting update happened last night. I downloaded a trial of QuickBooks Enterprise 2023, and it installed within five minutes.

I’m trying to run Process Explorer and Process Monitor, but am coming up short. If you have any expertise in either of these programs and troubleshooting what might be causing the install to fail with error 1603, please leave a comment below.

I FUCKING FIXED IT!

I used RegScan and performed a scan on all registry hives for “QuickBooks” and then exported them out and finally deleted them all.

I rebooted and sure enough it fucking installed. I knew it was a rogue fucking registry key. I hate Microsoft and Intuit!

For those of you who encounter the above issue and attempt to use PowerShell to run the Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} but the process never finishes, check the permissions on these two registry keys: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer and HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders – it should have a user called All Application Packages with read permissions.

In particular, the second one. I had an issue where the Get-AppX command would not complete on a Windows 10 Dell OptiPlex machine. I tried restarting to no avail.

I checked on the first registry key and All Application Packages were listed with read permissions for that key.

I checked the second, and All Application Packages were not there at all. I had to go to Advanced, Select a principal, if you’re on a domain, change the From this location: to the actual computer you’re using. Enter All Application Packages into the object name to select the box and hit OK.

Make sure it has read permission on the second registry key.

I rebooted the machine, and the start menu was working. I was also able to input the user’s Outlook password.