Your water mark has disappeared after the disabled Sppsvc.exe issue.
Your water mark has disappeared after the disabled Sppsvc.exe issue.
This topic isn't suitable for discussion here. I'm sorry, but I need to delete this thread and remove the moderator flag. I got frustrated because the service Microsoft uses was consuming my CPU, so I decided to reset it. Since I don’t use Outlook or Word, I wasn’t concerned about performance issues. The expected behavior was to show a water mark indicating a non-licensed Windows 10 installation. However, I haven’t activated my OS yet, and the water mark disappeared after several reboots and GPU adjustments. I’m confused because it seems to revert to a licensed appearance unexpectedly. Could there be something missing or an issue I’m not seeing?
It removes the watermark and also eliminates other features that are turned off when Windows isn't activated.
Im not sure the implications. Everything I read prior to doing this was that it would disable Microsoft Applications like Outlook, Word, (anything that requires a License check from Microsoft when you open it) because it couldn't communicate that license when it would try to. That and it would "un-authenticate" your Windows until you changed the Service back to "2" instead of "4" I will have to try changing Windows settings to check like you mention, great idea. There are certain things like Background etc that you cant manipulate when the water mark is present. Im hoping so! Ive multiple un-licensed rigs oddly...bwuahahaha
It's surprising that licensing Windows affects things like watermarks. If I don't have a license, the service should remove the mark automatically. The main point seems to be verifying whether services that normally require licensing are now working. I'll need to confirm this once I'm back home.
There are many guides explaining how to conceal the activation watermark; some suggest that disabling this service might achieve that, though it seems excessive. However, if it’s an unintended consequence of a previous issue, I think it could be a positive change!
Haha, I wasn't aware that the aim was to conceal it—it actually turned out to be a nice side effect of preventing MS from consuming MY CPU and draining MY power. I'm happy, just hoping it disappears now. I plan to rearrange components tonight to test if I can make it stop, then try it on my Ryzen setup and HTPC to compare results—my laptops are licensed, lol.