Windows 8.1 Pro Secure Build isnt configured correctly build 9600 watermark

http://support.microsoft.com/kb/2902864

http://support.microsoft.com/kb/2902864

the fix for  all problems

Guido from Belgium

@ Microsoft

I am from Germany. I also got this error message on several laptops after updating to win 8.1.  I am running i.e. an ASUS N76 and did also not found solution for this windows error.

So, I request you to fix this problem soon.

Regards

Thomas

Anannya Podder, I do not wish to enable secure boot. These machines are frequently re-imaged, often at short notice, and usually in large numbers. Having to disable secure boot in order to boot from an un-signed source, re-image, then re-enable secure boot afterwards will add considerable additional time and effort to an otherwise simple process, and require me to release supervisor passwords for BIOS access to individuals I do not wish to see poking around in the BIOS at all.

The number of issues stemming from Microsoft's misguided new design strategy (throwing more money into ideas that have already failed) are innumerable... but this isn't one of them - it's just obnoxious vandalism of my wallpaper and a lack of effort from Microsoft.

I don't want the build number and a redundant secure boot configuration warning on my desktop. I want it gone. Your response barely hints at the fact that Microsoft forgot to bother including an option to remove such a pointless and irritating watermark, and suggests that the user is at fault for being too stupid to enable secure boot, or the manufacturer for failing to provide a secure boot option.

I am not stupid, and my machine's manufacturer provides all the secure boot options I could ever wish for - however, I CHOOSE not to use secure boot as it provides no benefit with regard to the purpose of these machines, and using it would only serve as a source of ongoing frustration and stress.

With this in mind, how do I remove the watermark? It's a fairly simple question, the answer complicated only by oversights on the part of Microsoft, not by manufacturers or stupid users.

EDIT: I just saw the post a couple above mine (below the point to which I had previously read) with the fix linked. Thank you, Anannya, for taking the time to read this (if, indeed, you did). Perhaps you should edit your reply to include the new fix for those of us who unwittingly stumble upon this thread in our efforts to find a solution...

Thanks.....the update worked!