danke für deine Antwort.
Es sind 7 Windows 11 Geräte und ein Windows 10 Server alle auf der neues Update Version.
Es tritt auch beim Neustart auf ( Windows Schnellstart deaktiviert )
Läuft Der Computer länger als 1 Stunde tritt der Fehler sehr selten oder garnicht auf.
Deinstalliert man norton ist der Fehler komplett weg.
Das erste mal aufgetreten ist es vor 2 Wochen nachdem mal wieder eine neue Desktop Verknüpfung ungefragt angelegt wurde was ja meistens ein Zeichen für ein größeres Update von Norton ist.
Thanks for your reply.
There are 7 Windows 11 devices and one Windows 10 server, all running the latest update version.
The issue also occurs upon restarting (with Windows Fast Startup disabled).
If the computer runs for longer than one hour, the error occurs very rarely—or not at all.
If Norton is uninstalled, the error disappears completely.
It first appeared two weeks ago, after a new desktop shortcut was created without prompting—which is usually a sign of a major Norton update.
@Ronny What version/build of Windows 11 is installed?
Does the Windows 10 server use a straight edition of Windows 10 being used as a media server/local network file sharing, or, the actual W10 server installation? If the latter what is its release version? Does it also have Norton installed? Norton doesn’t support server OS products so how you are using the server may be conflicting with Norton.
Here are some thing you may want to try to temporarily resolve the issue:
Note: Do you have active RDP sessions when this occurs?
AI Overview
Windows 11 not shutting down completely is often caused by the “Fast Startup” feature, stuck system processes, or driver issues. To fix this, disable Fast Startup in Control Panel, update your system/drivers, or use a forced shutdown command (shutdown /s /f /t 0) in Command Prompt. [1, 2, 3]
Top Solutions to Fix Shutdown Issues:
Disable Fast Startup (Most Common Fix):
Open Control Panel and select Power Options.
Click “Choose what the power buttons do” on the left.
Click “Change settings that are currently unavailable” (requires admin rights).
Uncheck “Turn on fast startup (recommended)” and save changes.
Force Shutdown via Command Prompt:
Run cmd as administrator and type: shutdown /s /f /t 0.
Disable Hibernation:
Run powercfg /h off in Command Prompt to fully disable hibernation and force a complete shutdown.
Run System File Checker:
Run sfc /scannow in Command Prompt to repair corrupted system files.
Run Power Troubleshooter:
Go to Settings > System > Troubleshoot > Additional troubleshooters and run the Power troubleshooter. [1, 2, 3, 4, 5]
Immediate Temporary Workaround:
Hold down the Shift key while clicking Shut down in the Start menu. This forces a full shutdown regardless of settings.
If the screen is black but lights remain on, hold the physical power button for 5-10 seconds to force a hard shutdown
I have already run sfc /scannow, and it found no errors.
The only thing that helps is uninstalling Norton; therefore, the issue lies 100% with the current version of Norton. It started occurring right after the update—and the idea that 9 PCs (or their Windows installations) would fail simultaneously is highly unlikely.
I wasn’t entertaining the idea that several machines failed at once NOT being a Norton issue. I did ask whether there are RDP sessions active on the machines when this failure happened. How Norton is dealing with those may be a clue to the cause of the issue.
Other questions are:
What is your Norton history logging?
What does the Windows Event Viewer show regarding errors?
Do you have a crash dump file that can be reviewed by Norton?
My suggestion is, on one of the affected machines, download the Support Tool linked in this article. Follow the instructions and send the logs to Norton for review.
Strangely enough, no error is logged in the Windows Event Viewer—even though, if I were to shut down the PC right now using the power switch, at the very least an entry indicating that the PC shut down unexpectedly would be recorded. Furthermore, absolutely no errors are listed in the Windows Reliability Monitor. I’m just testing the Norton tool now; thanks for the suggestion.
Okay, looks like the translator didn’t translate everything there! No, I don’t have any logs—or rather, I wouldn’t know where Norton would store them, assuming it even generates any, since I’m not receiving any error messages.
The strange thing is that once the PC has been running for at least an hour or longer, it very rarely—if ever—has trouble shutting down; it’s only when you have to restart multiple times in quick succession—for things like Windows Updates or similar tasks—that the issue becomes noticeable.
Norton detections history is located in the settings area of the UI, under security history. Other areas to look for logging related to performance and other issues are:
Have a look at sui_user.log. It should open on its own when clicked and be readable.
Edited: You said you had a look at Windows Events Viewer and there were no entries. If this error has continued since your last clean install of Windows there should be entries related to the event ID’s 41 ( repeated 41 entries would indicate overheating ), event ID 1074 as it will identify the software causing the issues, event ID 6008 will indicate a “dirty” shutdown and more metadata should be readable. Please have another look at events viewer for these respective event ID entries.
No, I don’t have any logs—or rather, I wouldn’t know where Norton would store them, assuming it even generates any, since I’m not receiving any error messages.