Some Windows 7 systems unable to Shut Down or Restart

[rtwjunkie]

It appears that the month after MS ended all support for Windows 7, they may need to intervene with a fix. A number of users on MS forums, Reddit and other sites "are reporting that their Windows 7 systems refuse to shut down or reboot as they normally would, claiming that "you don't have permission to shut down this computer." Apparently it can be circumvented with some Group Policy command line actions. We shall see if MS issues Patch #2 following the End of Support.

Bug prevents Windows 7 users from shutting down their PCs

Microsoft was supposed to have ended Windows 7 support in mid-January, but it can't seem to completely let go -- and neither can some PCs, apparently. Many users on Microsoft's forums, Reddit and elsewhere are reporting that their Windows 7 systems refuse to shut down or reboot as they normally...

www.engadget.com

The first patch dealt with screensavers and can be read about here:

Microsoft forced to create a free Windows 7 update just days after updates ended

Microsoft is fixing an embarrassing Windows 7 bug it just introduced

www.theverge.com

 

[newtekie1]

I ran into this last night, the Group Police edit didn't fix the issue, though that might be because the computer was part of a domain so the domain was overriding the GP edit.

 

[lexluthermiester]

I have yet to encounter this issue. Do we know exactly what is causing it?

 

[delshay]

Works fine here no issues.

 

[rtwjunkie]

I have yet to encounter this issue. Do we know exactly what is causing it?

From the MS Forums it ranges from possible recent updates related to the crypt32.dll vulnerability or the Adobe genuine monitor service. MS is investigating, since there is not a consensus.

another read with some temp workaround steps:

Windows 7 Users Suddenly Can't Shut Down Their PCs, How to Fix

A "You don't have permission to shut down this computer." error is preventing Windows 7 from shutting down or restarting their computers according to user reports that came in during the last 24 hours.

www.bleepingcomputer.com

 

[StefanM]

If nothing else works, try Windows command "shutdown".

At first SHUTDOWN.EXE /? to get familiar with it.

 

[eidairaman1]

I have yet to encounter this issue. Do we know exactly what is causing it?

Probably an update

 

[xrror]

Thanks for the heads up, this showed up in our ticket system friday:

 

[lexluthermiester]

Probably an update

One of the very last ones likely. Microsoft trying to quietly sabotage 7 to force the hold-outs over to 10... It's only going to piss them off.

 

[eidairaman1]

One of the very last ones likely. Microsoft trying to quietly sabotage 7 to force the hold-outs over to 10... It's only going to piss them off.

Just like the previous update that bugged users.

 

[R-T-B]

One of the very last ones likely. Microsoft trying to quietly sabotage 7 to force the hold-outs over to 10... It's only going to piss them off.

If that was really their end game they wouldn't release free fixes for the issues.

I think it's that the crypt32.dll fix was very complex, and the resources dedicated to it on Windows 7 were minimal. No telling how much it really broke... a lot of systems use crypt32.

 

[lexluthermiester]

If that was really their end game they wouldn't release free fixes for the issues.

Good point!

 

[John Naylor]

There's a lot of money left on the table for MS. Win10 was MS's attempt to use the google model by making billions of dollars without actually "'selling" a product. Selling data to partners became the revenue stream to replace the licensing fee. When they fsiled to meet projections, partners dodn't have to ante up the monies projected on MS income sheets. Win 10 didn't overtake Win 7 to January 2019 ... now here in 2020, it still holds 1/3 market share ... we say all the conniving and tricks leading to unintended upgrades that brought an uproar. That will happens again as MS blames the sunset' for the problems intentionally introduced in these last few fixes.