Windows 10 Pro 64bit Shutdown Delay: Program Manager Interference and Potential Fixes

Hello,
For several days I have been struggling with the problem of long shutdown / restart of Windows 10. This happens before the system shutdown / restart - everything runs smoothly and quickly during startup. However, during the shutdown before shutdown / restart, the following message appears (taskmngr can not be taken into account, I did not turn off during this attempt):

I don't think I would install anything more than what I always had on my computer (the system is about 3 weeks after the complete hardware replacement). I was looking for a solution on the internet, but no results I cannot locate "program manager" at all - what it is, because it is not present in processes or services - at least not under that name, or at least a similar name. Below I am dropping the FRST logs - maybe someone will see something. And of course the PC + SMART specification.

Kill KMservice.exe process and restart. Message appears?

Added after 5 [minutes]:

Make a fixlist.txt like this:

S3 NTIOLib_1_0_C; \ ?? \ O: \ NTIOLib_X64.sys [X]
S3 NTIOLib_DVDSetup; \ ?? \ X: \ NTIOLib_X64.sys [X]
HKU \ S-1-5-21-2699839633-3818177318-1946132562-1001 \ ... \ MountPoints2: {1894fb58-d314-11e7-a021-806e6f6e6963} - "O: \ DVDSetup.exe"
HKU \ S-1-5-21-2699839633-3818177318-1946132562-1001 \ ... \ MountPoints2: {2aabf24e-d2e1-11e7-a02d-806e6f6e6963} - "X: \ DVDSetup.exe"
HKU \ S-1-5-21-2699839633-3818177318-1946132562-1001 \ ... \ MountPoints2: {c210589d-d2df-11e7-a02c-309c23462848} - "H: \ setup.exe"

Try uninstalling ESET. I don't know when you did this, but turn off processes one by one before rebooting and you'll find one that "holds" the reboot.

Added after 1 [minutes]:

SMART from the second disk provide.

Removal of the (complete) KMS had no effect. I am sending SMART of the second disk:

For now, I will make a fixlist and test. And then it will uninstall Eseta (if the first method doesn't help).

Uninstall
Opera Stable 44.0.2510.857
ADATA SSD ToolBox version 3.0.3 (HKLM-x32 \ ... \ {C0991D3E-8786-48E7-A5DB-57FBACB0A03A} _is1) (Version: 3.0.3 - ADATA, Inc.)

Execute another script like this:
Open the system notebook and paste:

Task: {005BBD8C-8CD8-4DE1-B590-DF231D582262} - System32 \ Tasks \ Opera scheduled Autoupdate 1511720559 => C: \ Program Files \ Opera \ launcher.exe [2017-11-23] (Opera Software)
Task: {0FA4346E-553A-448B-8FD8-DC3E49A91B70} - System32 \ Tasks \ Opera scheduled Autoupdate 1511771228 => C: \ Program Files \ Opera2 \ launcher.exe [2017-03-21] (Opera Software)
2017-11-27 09:27 - 2017-03-21 07:53 - 063944280 _____ () C: \ Program Files \ Opera2 \ 44.0.2510.857 \ opera_browser.dll
2017-11-27 09:27 - 2017-03-21 07:53 - 002101336 _____ () C: \ Program Files \ Opera2 \ 44.0.2510.857 \ libglesv2.dll
2017-11-27 09:27 - 2017-03-21 07:53 - 000087128 _____ () C: \ Program Files \ Opera2 \ 44.0.2510.857 \ libegl.dll
CHR HKLM-x32 \ ... \ Chrome \ Extension: [efaidnbmnnnibpcajpcglclefindmkaj] - hxxps: //clients2.google.com/service/update2/crx
S2 ADATA ToolBox Service; C: \ Program Files (x86) \ ADATA \ SSD ToolBox \ ToolBoxSvc.exe [6519296 2017-09-27] () [No digital signature]
EmptyTemp:

Save the file as fixlist.txt and put it in the folder where you have FRST.exe.
Run FRST and click Fix.

Opera causes some kind of error:
Faulting application name: launcher.exe_Opera Internet Browser, version: 44.0.2510.857, time stamp: 0x58d05d5b
Faulting module name: launcher.exe, version: 44.0.2510.857, time stamp: 0x58d05d5b
Faulting application path: C: \ Program Files \ Opera2 \ launcher.exe
And another error: Faulting Application Path: C: \ Program Files (x86) \ ADATA \ SSD ToolBox \ ToolBoxSvc.exe
Faulting module path: C: \ Program Files (x86) \ ADATA \ SSD ToolBox \ ToolBoxSvc.exe

The first fixlist did nothing. Uninstalling Eseta as well.
However, when it comes to Opera - the error probably causes the change of the file extension: opera_autoupdate.exe - now with a note .txt - I had to do this because version 44.0.2510.857 is the last one with all speakers working (Soundblaster X-Fi 5.1), thanks to adding a shortcut to the path: --force-wave-audio . Otherwise, only two work. And the extension has been changed, because Opera updates without user interaction and this is the only way I can use an older version of the browser. Launcher probably wants to run this file (maybe not directly) and hence these errors. Anyway, on the previous kit I was working the same way and the shutdown / restart problem did not occur.
Adata ToolBox - I removed it somewhere on the way, because it was one of the last programs I installed. I also fired all MSI applications, but it is still the same (above fixlist also made). No changes.

Maybe try to uninstall Pirate Office and get rid of:
() C: \ Windows \ KMService.exe
R2 KMService; C: \ Windows \ SysWOW64 \ srvany.exe [8192 2017-11-26] () [No digital signature]
2017-11-26 20:32 - 2017-11-26 20:31 - 000151552 _____ C: \ Windows \ KMService.exe
C: \ Windows \ SysWOW64 \ srvany.exe

Continue this way - the restart "holds" some Program Manager. The only one I see similar is:
R2 MSI_AppManager_Service; C: \ Program Files (x86) \ MSI \ APP Manager \ AppManager_Service.exe [2054096 2017-07-27] (MSI)
Please try to uninstall. What does this service do / provide at all? Overall you've got a ton of crapware and other wonders,

Did you kill processes before rebooting as advised?

KMS fired at the very beginning. Office reinstalled to a 30-day version. MSI - as I wrote before - all these applications were also uninstalled. After each uninstallation, I clean the registry with a cleaner.
The problem is that all of the above was installed in the first 2-3 days after the system was set up, i.e. around November 26-27, 2017, and the system has had problems with shutdown and restart times for about a week (maybe even less than a week). I would like to add that all of the above, which was removed (except the MSI application, because I got these from MOBO), I had installed on the previous PC configuration (LGA775) - there were no problems.
I haven't tested process killing yet, because we wrote at night, and now it's work - I'll check it in the evening.
As for "crapware" - would you replace me some? Assuming all the MSIs flew. I keep order and all the apps that seem unusual are installed for some purpose. I don't keep unnecessary things.

Run the cmd window with administrator rights and enter there:
reg add "HKCU \ Control Panel \ Desktop" / v "AutoEndTasks" / t REG_SZ / d 1 / f
reg add "HKCU \ Control Panel \ Desktop" / v "HungAppTimeout" / t REG_SZ / d "5000" / f
reg add "HKCU \ Control Panel \ Desktop" / v "WaitToKillAppTimeout" / t REG_SZ / d "10000" / f

This should accelerate the closure.

It's also worth doing a clean boot:
https://support.microsoft.com/pl-pl/help/929135/how-to-perform-a-clean-boot-in-windows
Then run one at a time until you find the application that is causing the problem.

Unfortunately, none of the above methods contributed to anything. I'm starting to suspect some system update or system process. In any case, "program manager" does not belong to any of the applications I have installed. I keep searching.

It is part of the system, not an installed application.

Still blocking after performing a clean boot?

https://www.google.pl/search?q=program+manager+windows+10+shutdown
As you can see, not only you have such a problem.

Yes - all reset according to the instructions. I even went into safe mode with no network support - it was also coming out for a long time.

Read the google results from the MS forum, maybe you will find a solution.

I checked all the possibilities from this forum yesterday. I have reviewed them before and many others. I dug the internet - there is probably no solution to this problem. If I feel like it and there is time, I will simply put the system back up again, not being sure if the problem will not appear again. Perhaps an update will fix it. Or I will simply live with it - there is no tragedy - long shutdown and restart is not that troublesome - the most important thing is that it starts up in several seconds I am closing the topic at the moment - if I find a solution - I will open it and describe how I coped.

Of course, thanks for your help and tips.