Since scrolling is initially enabled, it's safe to conclude that this CSS setting is not in any of the style sheets or the initial content as parsed by the browser — such parsing is done before the content is rendered. Therefore, it is being set by Javascript. It appears to be an intentional "evil CSS" choice.
The web is full of CSS trickery, of course, but usually businesses aren't so obvious about it.
its working, back in the old days it was called Palladium and was widely rejected as the experts knew what their endgame was, 20 years later with a rebrand into TPM with enforcement baked in and its a resounding success, any hacker knows if it has Trust in the product name its anything but trustworthy.
not that easy pal, you have to follow the rabbit, Win10 has multiple watchdogs that periodically check to see if WindowsUpdates services or any parts of the update system are disabled/broken/corrupt, if it finds issues the watchdog processes will re-enable/repair updates, the reason being is many malware apps used to disable updates so now a watchdog checks.
It is possible to disable it but long gone are the days that simply disabling WindowsUpdate in services.msc would stop it.
Work is the crab grass in the lawn of life. -- Schulz