Born: “You don’t have permission to shut down and restart this computer” bug now evident on Win10 machines

Topic

New Reply

Remember the problem reported two weeks ago, where Win7 would stall on shut down, displaying the message “You You don’t have permission to shut down t
[See the full post at: Born: “You don’t have permission to shut down and restart this computer” bug now evident on Win10 machines]

Reply | Quote

Replies

It’s easier to just blame Windows updates 😀

2 users thanked author for this post.

ryegrass, woody

Reply | Quote

Very true, and I’ve been guilty of that many times.

Reply | Quote

Direct link to post by PaulSey…: https://answers.microsoft.com/message/91921284-e293-4d4e-bcd0-265abb5d8f28?threadId=c08d3cee-1f87-498b-b8b8-7fb06a20755d

Same post in another thread: https://answers.microsoft.com/message/58ba1b1d-72e2-4627-8f62-d5acdf265b00?threadId=4664c0c9-e93d-4612-b863-caebb89b6d35

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

Günter Born is back with repeated reports that the same message now appears on Win10 machines:

Only one report there, a week ago.

woody wrote:

Looks like the prime suspect is Adobe Creative Cloud but Born also points the finger at BitDefender Total Security and the January .NET Framework 4.8 patch.

You omitted “It’s not Microsoft’s fault … Reporting otherwise is irresponsible.”!

woody wrote:

Born has a link to Microsoft’s admission that the patch exists:

Patch or problem?

woody wrote:

On February 13, 2020, Paul Sey, Microsoft employee and owner of Microsoft Answers forum wrote here:

“We’ve identified and resolved the issue, which was related to a recent Adobe Genuine update that impacted a small number of Windows 7 users. Adobe has fully rolled back the update automatically for all impacted customers. No action is needed by customers. If you are still experiencing the issue, it will be resolved shortly via an automatic update.”

But, as you can readily confirm, either the link is bad or Microsoft has yanked it.

That comment is still at the bottom of page 1 of replies at that link, and duplicated at the top of page 4 of replies in this similar thread: windows 7 problem not shutdown

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

1 user thanked author for this post.

woody

Reply | Quote

From the same Twitter thread:

If/when someone finally comes clean, I expect Adobe to be the clear culprit. I expect a ho-hum patch or rollback with the hopes that no one notices. For now, however, dead silence on the issue, so we wait.

1 user thanked author for this post.

b

Reply | Quote

Well, the good news is that I don’t use Adobe Creative Cloud nor BitDefender Total Security and I haven’t installed .NET Framework 4.8 at all on my 1809 machine (so none of the 4.8 patches are installed here). The bad news is that if this starts happening on my computer then we will have to figure out an entirely different culprit… 😉

Reply | Quote

Fully updated Version 1909 (OS Build 18363.657) shuts down just fine, although that’s something I very, very rarely do.  I just sign out, because Task Scheduler has things to do when I don’t.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

1 user thanked author for this post.

doriel

Reply | Quote

UPDATE: Paul Sey’s comment is back — I could’ve sworn it wasn’t there early this morning when I checked. Thx to the commenters who pointed me to it! I note in passing that it still hasn’t been added to the Release Information Status page — perhaps because Microsoft considers it to be an Adobe bug.

1 user thanked author for this post.

b

Reply | Quote

I do run Adobe Creative Cloud for photo apps but my Win10 updates are delayed for 16 days so I don’t have any of the recent patches installed.  I’m on 1909 build 18363.592 and it will be updated next week.  We’ll see what happens then!!

Reply | Quote