Boot scan took 6 hours, then told me my 'Windows' was not genuine?

Hello Stephen,

We will check this for you.
The error message you received occurs because either you are not running a genuine copy of Windows or your license got expired.
There is also a chance that a windows update can cause this problem.
To check if your windows is genuine or not, go to Start >> Control Panel >> System and Security >> System.
Then scroll down to the bottom and you should see a section called Windows activation, which says “Windows is activated” and gives you the Product ID.
Kindly check if your Windows is up to date update and also share us the screenshot of the message you received.

I used the 'boot' scan function for the first time and the scan took almost 6 hours! It did quarantine numerous files and deleted some, so that is fine. However, when it did finish, and start to boot up, it displayed a black screen with the following message in the bottom right of screen stating, "Windows 7, Build 7601, This copy of Windows in not genuine".

I had a real butt clenching moment on seeing this, but after a few minutes, it commenced booting up as normal, so all well.

Now, in 30 odd years, I've had my fair share of 'dodgy' software, but my laptop was bought from a proper national chain of computer retailers, and the Windows is 100% genuine. So, why did I get that message, and will I get it every time on doing a 'boot' scan?

 

Hello Stephen,

We will check this for you.
The error message you received occurs because either you are not running a genuine copy of Windows or your license got expired.
There is also a chance that a windows update can cause this problem.
To check if your windows is genuine or not, go to Start >> Control Panel >> System and Security >> System.
Then scroll down to the bottom and you should see a section called Windows activation, which says “Windows is activated” and gives you the Product ID.
Kindly check if your Windows is up to date update and also share us the screenshot of the message you received.

I've no idea why I didn't 'google' it in the first place, this 'error' has loads of listings, and is ironiclally caused by a genuine MS Update a few years back! Anyway, easily solved…

https://www.youtube.com/watch?v=HY9TA3RdEWQ

Thank you the screenshot, Stephen
In this case, I request you to consult from the Windows Support.
They will let you know why that message came in the first place.