cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Sdidi
Ctrl-Alt-Del
Posts: 7
Registered: ‎10-15-2019
Location: CH
Views: 345
Message 1 of 6

"pending reboot" hanging in the Softwarecenter

Some clients have the message in the Softwarecenter that a reboot is hanging after the driver installation. It tries to install the same driver indefinitely. The Lenovo drivers that have been deployed have the pending reboot hanging in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

This problem also occurs with newly imaged devices with the LUC Agent (Windows 10, Build 1803).

The following errors are visible in the Lenovo LUC Agent STDeploy.log:

2019-10-30T08:07:03.9008832Z 4538 I STPackageDeployer.cpp:1235 Patch file 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-04-26\n1wa115w.exe' install operation completed. Cooked result='6'. RebootRequired='true'
2019-10-30T08:07:03.9008832Z 4538 I STPackageDeployer.cpp:1963 Done deploying patches...
2019-10-30T08:07:03.9008832Z 4538 I STPackageDeployer.cpp:1965 Deploying product instances patches...
2019-10-30T08:07:03.9008832Z 4538 I STPackageDeployer.cpp:2005 Done deploying product instances patches...
2019-10-30T08:07:03.9018810Z 4538 W SingleInstanceLock.cpp:28 Waiting for another deployment to finish.
2019-10-30T08:07:03.9018810Z 4538 I SingleInstanceLock.cpp:36 Exclusively continuing deployment.
2019-10-30T08:07:03.9018810Z 4538 V STPackageDeployer.cpp:85 Initiating patch store servicing.
2019-10-30T08:07:03.9018810Z 4538 V STPackageDeployer.cpp:106 Patch store servicing complete.
2019-10-30T08:07:03.9038756Z 4538 I STPackageDeployer.cpp:1378 Scheduling a relaunch of STDeploy.exe at next bootup to perform post-boot actions processing
2019-10-30T08:07:03.9048734Z 4538 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (94d8c192-1930-4187-8207-db449633516a), comment=Schedule STDeploy.exe to run at next bootup to perform post-boot actions.
2019-10-30T08:07:03.9048734Z 4538 V Scheduler.cpp:82 AddJob A. local machine
2019-10-30T08:07:03.9068676Z 4538 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:03.9068676Z 4538 V Scheduler.cpp:97 AddJob B.
2019-10-30T08:07:03.9078645Z 4538 V Scheduler.cpp:206 CreateTask 1.
2019-10-30T08:07:03.9088619Z 4538 V Scheduler.cpp:234 Creating trigger type 6.
2019-10-30T08:07:03.9088619Z 4538 V Scheduler.cpp:856 isTimeInPast
2019-10-30T08:07:03.9098592Z 4538 V Scheduler.cpp:100 AddJob C.
2019-10-30T08:07:03.9268143Z 4538 V Scheduler.cpp:107 Using the local system account
2019-10-30T08:07:03.9268143Z 4538 V Scheduler.cpp:126 AddJob D.
2019-10-30T08:07:03.9308036Z 4538 I STPackageDeployer.cpp:974 'STDeploy.exe package="deployPackage.zip" relaunchSandbox="C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-04-26" relaunchReason="afterPostDeploymentReboot=1"' scheduled to run on next boot-up.
2019-10-30T08:07:03.9308036Z 4538 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:03.9308036Z 4538 I STPackageDeployer.cpp:500 Reporting external reboot required
2019-10-30T08:07:03.9308036Z 4538 E DeployStatusReporter.cpp:99 No handler for external reboot!
2019-10-30T08:07:03.9308036Z 4538 E DeployStatusReporter.cpp:112 Error 50l returned from external reboot request.
2019-10-30T08:07:03.9308036Z 4538 S DeployExeStates.cpp:409 Leaving STDeploy::CInitialExecutionPackageDeploy:Smiley Very HappyoStatefulRemediateActions.
2019-10-30T08:07:03.9308036Z 4538 I STDeploy.cpp:365 Current remediation phase completed. Process exit code: 3010.
2019-10-30T08:07:03.9308036Z 4538 S STDeploy.cpp:257 Leaving wmain.
2019-10-30T08:07:04.6508771Z 4de4 S STDeploy.cpp:257 Entering wmain.
2019-10-30T08:07:04.6518744Z 4de4 I STDeploy.cpp:262 'C:\WINDOWS\SoftwareDistribution\Download\Install\STDeploy.exe' is starting, version: 9.3.17101.0.
2019-10-30T08:07:04.6518744Z 4de4 V DeployContext.cpp:259 STDeploy.exe command line args: 'package="C:\WINDOWS\SoftwareDistribution\Download\Install\deployPackage.zip" "removeStaging=yes" "baseDir=%ProgramData%\Lenovo\Lenovo Patch"'
2019-10-30T08:07:04.6518744Z 4de4 S DeployExeStates.cpp:344 Entering STDeploy::CExtendedCmdLineHandlingPackageDeploy:Smiley TonguerocessExtendedCmdLineArguments.
2019-10-30T08:07:04.6518744Z 4de4 S DeployExeStates.cpp:344 Leaving STDeploy::CExtendedCmdLineHandlingPackageDeploy:Smiley TonguerocessExtendedCmdLineArguments.
2019-10-30T08:07:04.6857841Z 4de4 S DeployExeStates.cpp:401 Entering STDeploy::CInitialExecutionPackageDeploy:Smiley FrustratederviceDeploymentSandboxes.
2019-10-30T08:07:04.6907707Z 4de4 V DeployExeStates.cpp:60 Created new deployment sandbox at 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04'
2019-10-30T08:07:04.6917681Z 4de4 S DeployExeStates.cpp:401 Leaving STDeploy::CInitialExecutionPackageDeploy:Smiley FrustratederviceDeploymentSandboxes.
2019-10-30T08:07:04.6917681Z 4de4 V STDeploy.cpp:135 initialLogFilePath='C:\WINDOWS\SoftwareDistribution\Download\Install\STDeploy.log' permanentLogFilePath='C:\ProgramData\Lenovo\Lenovo Patch\Logs\STDeploy.log' sandboxLogFilePath='C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\STDeploy.log'
2019-10-30T08:07:04.6917681Z 4de4 I STDeploy.cpp:143 Preparing to Move initial trace logs to the permanent logfile at 'C:\ProgramData\Lenovo\Lenovo Patch\Logs\STDeploy.log'.
2019-10-30T08:07:04.6927650Z 4de4 I STDeploy.cpp:167 Trace logging transferred from 'C:\WINDOWS\SoftwareDistribution\Download\Install\STDeploy.log'.
2019-10-30T08:07:04.6927650Z 4de4 V STDeploy.cpp:171 Moved initial trace logs to the logfile at 'C:\ProgramData\Lenovo\Lenovo Patch\Logs\STDeploy.log'.
2019-10-30T08:07:04.6947605Z 4de4 I STDeploy.cpp:331 Relaunching STDeploy.exe to run out of a sandbox at 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04'.
2019-10-30T08:07:04.9022051Z 4f30 S STDeploy.cpp:257 Entering wmain.
2019-10-30T08:07:04.9022051Z 4f30 I STDeploy.cpp:262 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\STDeploy.exe' is starting, version: 9.3.17101.0.
2019-10-30T08:07:04.9032061Z 4f30 V DeployContext.cpp:259 STDeploy.exe command line args: 'package="C:\WINDOWS\SoftwareDistribution\Download\Install\deployPackage.zip" "removeStaging=yes" "baseDir=%ProgramData%\Lenovo\Lenovo Patch"'
2019-10-30T08:07:04.9032061Z 4f30 S DeployExeStates.cpp:344 Entering STDeploy::CExtendedCmdLineHandlingPackageDeploy:Smiley TonguerocessExtendedCmdLineArguments.
2019-10-30T08:07:04.9041997Z 4f30 S DeployExeStates.cpp:344 Leaving STDeploy::CExtendedCmdLineHandlingPackageDeploy:Smiley TonguerocessExtendedCmdLineArguments.
2019-10-30T08:07:04.9520712Z 4f30 I STDeploy.cpp:358 C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\STDeploy.exe is now executing out of a sandbox: 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04'.
2019-10-30T08:07:04.9520712Z 4f30 S DeployExeStates.cpp:409 Entering STDeploy::CInitialExecutionPackageDeploy:Smiley Very HappyoStatefulRemediateActions.
2019-10-30T08:07:04.9520712Z 4f30 V DeployExeStates.cpp:84 Invoking remediation manager processing: userSuppliedFileName='deployPackage.zip', userSuppliedPath='C:\WINDOWS\SoftwareDistribution\Download\Install', patchStorePath='C:\ProgramData\Lenovo\Lenovo Patch\Patches', deployerCoreLogFilePath='C:\ProgramData\Lenovo\Lenovo Patch\Logs\STDeployerCore.log', LaunchCount='0', LaunchReason='0', currentDirectory='C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04', sandboxDirectory='C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04'
2019-10-30T08:07:04.9520712Z 4f30 I STPackageDeployer.cpp:1589 Moving files from stagingDirectory 'C:\WINDOWS\SoftwareDistribution\Download\Install' to sandbox directory 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04'
2019-10-30T08:07:04.9530694Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\7z.dll' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\7z.dll'.
2019-10-30T08:07:04.9550632Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\CL5.exe' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\CL5.exe'.
2019-10-30T08:07:04.9590530Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\customPatch.xml' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\customPatch.xml'.
2019-10-30T08:07:04.9610476Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\DeployManifest.xml' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\DeployManifest.xml'.
2019-10-30T08:07:04.9620450Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\deployPackage.zip' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\deployPackage.zip'.
2019-10-30T08:07:04.9640396Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\n2hku54w_x64.exe' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\n2hku54w_x64.exe'.
2019-10-30T08:07:04.9660335Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\SafeReboot.exe' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\SafeReboot.exe'.
2019-10-30T08:07:04.9680285Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\SafeReboot64.exe' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\SafeReboot64.exe'.
2019-10-30T08:07:04.9690320Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\STDeploy.log' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\STDeploy.log'.
2019-10-30T08:07:04.9710201Z 4f30 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\WINDOWS\SoftwareDistribution\Download\Install\STDeployerCore.dll' to 'C:\ProgramData\Lenovo\Lenovo Patch\Installation\InstallationSandbox#2019-10-30-T-08-07-04\STDeployerCore.dll'.
2019-10-30T08:07:05.0946901Z 4f30 I STPackageDeployer.cpp:1595 Deleted staging directory 'C:\WINDOWS\SoftwareDistribution\Download\Install'
2019-10-30T08:07:05.1106478Z 4f30 I STPackageDeployer.cpp:847 Deploy package 'deployPackage.zip' successfully opened unsigned for package IO
2019-10-30T08:07:05.1106478Z 4f30 I STPackageDeployer.cpp:192 All required parts found in the deployment package.
2019-10-30T08:07:05.1116455Z 4f30 I STPackageDeployer.cpp:673 Deploy id ('a51ae0af-ca29-4dbc-a3b3-bd269120a823'), machine id ('127001'), deployerCoreVersion ('9.3.2708.0')
2019-10-30T08:07:05.1146371Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {a51ae0af-ca29-4dbc-a3b3-bd269120a823}, comment=deleting job.
2019-10-30T08:07:05.1256065Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:05.1256065Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=Scheduled Deployment {a51ae0af-ca29-4dbc-a3b3-bd269120a823} with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:05.1256065Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:05.1256065Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {a51ae0af-ca29-4dbc-a3b3-bd269120a823}, comment=deleting job.
2019-10-30T08:07:10.1320061Z 4f30 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='Scheduled Deployment {a51ae0af-ca29-4dbc-a3b3-bd269120a823}'
2019-10-30T08:07:10.1320061Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:10.1368291Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:10.1378281Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtBootup (a51ae0af-ca29-4dbc-a3b3-bd269120a823) with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:10.1378281Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:10.1378281Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:15.1407236Z 4f30 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtBootup (a51ae0af-ca29-4dbc-a3b3-bd269120a823)'
2019-10-30T08:07:15.1407236Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:15.1457058Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:15.1466998Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (a51ae0af-ca29-4dbc-a3b3-bd269120a823) with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:15.1466998Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:15.1476972Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:20.1517374Z 4f30 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (a51ae0af-ca29-4dbc-a3b3-bd269120a823)'
2019-10-30T08:07:20.1517374Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:20.1575552Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:20.1575552Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForDeployAfterPreDeployReboot (a51ae0af-ca29-4dbc-a3b3-bd269120a823) with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:20.1575552Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:20.1585521Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:25.1621845Z 4f30 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForDeployAfterPreDeployReboot (a51ae0af-ca29-4dbc-a3b3-bd269120a823)'
2019-10-30T08:07:25.1631810Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:25.1711515Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:25.1721464Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForOnlineStatusRetry (a51ae0af-ca29-4dbc-a3b3-bd269120a823) with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:25.1721464Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:25.1721464Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:30.1764893Z 4f30 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForOnlineStatusRetry (a51ae0af-ca29-4dbc-a3b3-bd269120a823)'
2019-10-30T08:07:30.1764893Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:07:30.1774752Z 4f30 V Task.cpp:32 Task connected MS 2.0 scheduler
2019-10-30T08:07:30.1774752Z 4f30 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForPostBootActions (a51ae0af-ca29-4dbc-a3b3-bd269120a823) with the scheduler 2.0 interface installed - will not try AT interface
2019-10-30T08:07:30.1784717Z 4f30 V Task2.cpp:99 Task2 destructor
2019-10-30T08:07:30.1784717Z 4f30 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (a51ae0af-ca29-4dbc-a3b3-bd269120a823), comment=deleting job.
2019-10-30T08:

Lenovo Staff
Lenovo Staff
Posts: 1,251
Registered: ‎03-03-2016
Location: US
Views: 268
Message 2 of 6

Re: "pending reboot" hanging in the Softwarecenter

@Sdidi,

 

I will take a look at this and see if I can reproduce the error.

 

TLawson

Sdidi
Ctrl-Alt-Del
Posts: 7
Registered: ‎10-15-2019
Location: CH
Views: 254
Message 3 of 6

Re: "pending reboot" hanging in the Softwarecenter

Here an example of Lenovo T470s

It seems like it tries to install older drivers which are not superseded every time the system is restarted.

L1.PNGL3.PNG

Here you can see that the driver is not compatible if the Setup.exe is executed manually.


L4.PNG

Here is a list of the drivers that appear after each restart.


This problem was also detected with other Lenovo types. I think Lenovo needs to develop the Detection Keys better, otherwise we have this problem all the time.

Lenovo Staff
Lenovo Staff
Posts: 1,251
Registered: ‎03-03-2016
Location: US
Views: 220
Message 4 of 6

Re: "pending reboot" hanging in the Softwarecenter

@Sdidi,

 

I cannot reproduce your errors you are showing in the OP or in the second post.  I deployed a T470s with 1803.  I made sure to deploy with the 1803 driver pack. After the computer has deployed, I wait for it to process through the following collection hierarchy.

 

Here is my collection hierarchy for applying Lenovo Updates.

 

Lenovo - Limiting Collection = All Systems, Query Membership looking for Computer System Product.Vendor is equal to "LENOVO" (Requires Hardware Inventory scan and membership update) - Deploy LUCAgent 1.0.0.5 to this collection.

Lenovo Devices with LUCAgent Installed - Limiting Collection = Lenovo (above), Query Membership looking for LUCAgent in Installed Appliations.DisplayName is equal to Lenovo UpdatesCatalogAgent (Requires Hardware Inventory scan and collection membership update) - No Deployments here.  ***Note:  The "Lenovo Devices with LUCAgent Installed" collection is an important collection. It ensures the Agent is present prior to deploying updates.  If the Agent is not present prior to deploying updates, the IsInstalled Rules will not have a WMI Class required for executing the detection rules. ***

ThinkPad T470s with LUCAgent - Limiting Collection = Lenovo Devices with LUCAgent Installed, Query Membership looking for ComputerSystemProduct.Version is equal to ThinkPad T470s (Requires collection membership update) - Deployed the T470s SUG with the listed updates in your OP.

 

I found the 3 updates you show in your first post, Lenovo Power Management Driver 1.67.17.28 (n2hku54w_x64), Synaptics Metallica MOC Touch Fingerprint Driver 5.2.3536.26 (n1mgf14w), and the Realtek Audio Driver 6.0.1.8642 (n1wa115w).

 

I created a Software Update Group with the 3 updates, created a Software Update Deployment Package with the downloads of the 3 updates and distributed to my DPs.  I deployed the SUG with the 3 updates to my ThinkPad T470s with LUCAgent collection.  When I create an update deployment, I make sure to check the box on the User Experience page in the section "Software updates deployment re-evaluation behavior upon restart".  The check box is "If any update in this deployment requires a system restart, run updates deployment evaluation cycle after restart."  A few moments after restart, if I refresh the updates section of Software Center, the updates disappear.  On the client, can you run the Configuration Manager Actions for Software Updates Deployment Evaluation Cycle after a reboot and see if it removes the updates from Software Center?

 

From the console, I can run a summarization on my updates and SUGs.  After the summarization completes and I refresh all the data, my SUG update statistics resolve and I show that those computers have moved from Required to Installed.  

 

When you say:

 


@Sdidi wrote:

Here an example of Lenovo T470s

It seems like it tries to install older drivers which are not superseded every time the system is restarted.


I am not sure I follow what you mean.  When an update is installed, it is not superseded, it moves from required to installed.  Supersedence is only when the update has a newer version.  The drivers you show are the most recent versions in the catalog.  All previous drivers to the ones indicated have been superseded.  I dont see any older ones attempting to apply.

 

In the first picture of your previous post, you are reviewing the incorrect device in device manager for the Realtek Audio Driver.  To confirm, if you click on the the Details Tab and change the property in the drop down list to Hardware Ids or Compatible Ids, none listed will be Realtek device ids.  These will be Audio Endpoints built by Windows, which is why there is a driver version of 10.0.17134.1 and a Driver Provider of Microsoft. To review the correct device, in device manager, navigate to Sound, video, and game controllers.  In that class, there will be a Realtek High Definition Audio device.  Again, select the Details tab and choose Hardware Ids or Compatible Ids.  You will see IDs in there for HDAUDIO\FUNC_01&VEN_10EC&DEV_0298 and on.  10EC is the vendor ID for Realtek.

 

In the second picture of your previous post, I cannot reproduce the manual installation issue of the Realtek Driver on a T470s with the n1wa115w package from the ccmcache and extracted to test with.  Where did you obtain the installer?

 


@Sdidi wrote:

Here an example of Lenovo T470s

This problem was also detected with other Lenovo types. I think Lenovo needs to develop the Detection Keys better, otherwise we have this problem all the time.

You have already mentioned detection methods, which are the IsInstalled rules, in another post and I have already addressed that we are working on rectifying those, but they do not seem to be at play in this instance.  The IsInstalled rules you mentioned come into play regarding reporting in the console, but do not really cause issues on the client side.  Now, I say they do not appear to be at play in this instance because for an update to be applicable to the device the IsInstalled rules would need to resolve as false and the IsInstallable section would have to resolve true.  Since you see them as available updates in Software Center on the client and they are installing, the detection rules are working as expected.

 

To also address you finding the key in the registry for a required reboot, through all of my testing, I cannot reproduce that.  When are you checking that key? Prior to the restart or after?

 

TLawson

Sdidi
Ctrl-Alt-Del
Posts: 7
Registered: ‎10-15-2019
Location: CH
Views: 196
Message 5 of 6

Re: "pending reboot" hanging in the Softwarecenter

The collection hierarchy looks quite similar here:

 

LUC Agent Deployment:
Limiting collection: Only Office Network Clients
Query Rule:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Manufacturer like "%Lenovo%"


Lenovo Devices with LUCAgent Installed:

Limiting collection: Only Office Network Clients

Query Rule:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Lenovo UpdatesCatalogAgent"

Since we deploy the updates in 3 phases, I have created two additional collections limited to Lenovo Devices with LUCAgent Installed with ~250 clients with 33 different Lenovo Hardware Types.

 

The Software Updates Deployment Evaluation Cycle was executed several times, unfortunately without improvement. 


The checkbox in the User Experience on SUG is checked by default as we have the same settings for Microsoft updates:
SUG1.JPG

 

I especially noticed that the same driver updates were present in the "Installation" folder with different download dates:

C:\ProgramData\Lenovo\Lenovo Patch\Installation

The registry key will be created automatically a few seconds after the driver installation. For other clients, the keys were automatically deleted after the first restart. Since this problem occurred on three Lenovo T470s, one T480s I thought it might be a general problem.

For a client, the pending reboot changed to compliant after I reinstalled the LUC Agent - What could be the reasons for this?

I will keep an eye on it and report if the problem still exists to start with the next deployment phase.

 

To your question, where did I get the setup file from, quite simply, from: C:\ProgramData\Lenovo\Lenovo Patch\Installation. This will extract the setup file to C:\DRIVERS. 
I agree with you; It is a confusion because the audio driver is displayed in the Device Manager at the top of the operating system with German language pack, but not in the English operating system - In this case I have to check the driver version again.

 



Highlighted
Lenovo Staff
Lenovo Staff
Posts: 1,251
Registered: ‎03-03-2016
Location: US
Views: 142
Message 6 of 6

Re: "pending reboot" hanging in the Softwarecenter

@Sdidi,

 

You mentioned that you reinstalled the LUCAgent and things started working appropriately.  Have your performed an inplace upgrade from a previous Windows 10 version to the current version (1803 I believe if I recall)?  

 

If you have run an inplace upgrade, you will need to uninstall and reinstall the LUCAgent.  You can run that as part of the IPU Task Sequence.  Here is a link to my KB post regarding uninstall and reinstall of the LUCAgent in an IPU Task Sequence.

 

TLawson

 

 

Check out current deals!


Shop current deals

Top Kudoed Authors