Third-party Authorization process thinks my computer is two different computers every shut down

Question

I've have a strange issue with a third party app's authorization process throwing errors because it thinks, after every shut down, my computer is a different computer (it flip flops between recognizing two different log ins). I've been in contact with the developer of the app, which I feel I should keep private, but they said their app uses a third party authorization process, but all I know is it 'digs into system stuff' to determine if the computer is indeed the same computer that was authorized. Nevertheless, for some reason it thinks my computer is two different computers, and it flip flops every shut down (the dev has relayed this from what he can see on his end). So if I authorize with a new license, shut down twice, it throws no errors. It appears to have begun after I updated the app, but it seems I'm the only one with the issue which points the finger at my computer (someone else did have the issue but the newer update fixed it for them).

I use no virtual machines and haven't changed hardware at all, save new RAM I got awhile ago (before this issue started, but feel I should mention any and all possibilities at this point.)

Steps I've tried

-trying to set a static MAC addy (based on a forum search I did, but the app dev doesn't think this MAC address should cause issues since Apple changes MAC addresses all the time. And also I use a wifi adapter anyway)

-restarting four times (based on same forum post, which seemed to be related to a 'hidden account' sometimes signing in, but the issues were not very similar to mine and this was a shot in the dark)

-cursing the digital gods

We are both pretty stumped, and any and all suggestions are welcome.

Answer 1

Hi

Thanks for your reply.

Anyway, I'm glad that your problem has finally been resolved. If you encounter any new issues in the future, feel free to start a new thread to ask questions, and we will do our best to assist you.

Best regards

Derrick Qian | Microsoft Community Support Specialist

Answer 2

Thank you for all the ideas -- so the app worked after disabling non-MS services and disabling startup apps, but then kept working after I reinstated all of them... the only other thing that changed this morning was a windows update that installed itself (which I suppose I'm thankful for!)

I did have issues with a previous windows update (seemed to cause slower startup and responsiveness in general), that I uninstalled and then it reinstalled itself (I have auto updates OFF btw, but windows doesn't seem to care) -- which caused a HD integrity error that windows then fixed... but this was around the time of the app update that seemed to cause issues.

In the end, I don't know why it's working now -- it does seem like some sort of windows related issue, that the recent update fixed (I don't see why cycling ON/OFF the services and startup programs would fix it)

Answer 3

Hi

Welcome to Microsoft community.

The issue you're describing, where a third-party app's authorization process mistakenly identifies your computer as two different systems upon each shutdown, is certainly unusual and understandably frustrating. It seems like the authorization mechanism the third-party app uses is sensitive to certain system characteristics that it perceives as changing between sessions. Here are several steps and considerations that might help resolve or isolate the problem:

System Time and Date Consistency

Check if your system's time and date are consistent and automatically syncing. Sometimes, significant inconsistencies in system time and date can affect software behavior.

• Go to Settings > Time & Language > Date & Time to ensure your time and date are set to automatic.

Network Adapter Settings

Since you mentioned attempting to set a static MAC address and are using a WiFi adapter, ensure that the adapter settings are not being reset upon each reboot. Some systems or third-party software might reset these settings for security or configuration reasons.

Windows System Restore

If the issue started occurring after an update to the app, consider using Windows System Restore to revert your system to a state before the update was applied. This can help determine if the update is indeed the cause.

• Search for Create a restore point in the Start menu, open it, and see if you have a system restore point available before the issue began.

Check for System File Corruption

System file corruption could potentially cause unusual behavior. Running a system file check might identify and fix any corrupted files.

• Open Command Prompt as Administrator and run  sfc /scannow  to check for system file integrity.

Hardware IDs and System Information

Some authorization systems use hardware IDs or specific pieces of system information to identify a device uniquely. Since you've mentioned adding new RAM, even though it was a while ago, it's worth checking if removing the new RAM changes the behavior (as a test, not a solution).

Update Drivers and BIOS/UEFI Firmware

Outdated drivers or firmware can sometimes cause unexpected issues. Ensure all your system drivers, especially for the motherboard and network adapters, are up to date. Similarly, check if there's a BIOS/UEFI firmware update available for your system.

Disclaimer:  Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.   If you are going to modify BIOS Settings, please back up all your personal files first to ensure you do not lose data.

Clean Boot

Perform a clean boot to start Windows with a minimal set of drivers and startup programs. This can help determine if background software is causing the issue.

• Press Windows Key + R, type msconfig and press Enter. Go to the Services tab, check Hide all Microsoft services, and then click Disable all. Next, go to the Startup tab and disable all startup items. Restart your computer and see if the issue persists.
• Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.    These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.

Consult the Developer Again

Since the issue is specific to the app and its authorization process, keep the lines of communication open with the app's developer. Share your findings from the above steps. They might have insights or be able to adjust the authorization process based on new information.

Consider System Reinstallation

As a last resort, if the issue severely impacts your use of the app and no other solutions have worked, consider backing up your data and performing a clean installation of your operating system. This can ensure that any system-level changes that might be affecting the authorization process are reset.

Given the specificity of the issue, there might not be an immediate or simple solution, but these steps should help in further isolating and potentially resolving the problem.

Please feel free to let me know how it goes.

Best regards

Derrick Qian | Microsoft Community Support Specialist