Windows 10: Workstation seems to patch but does not show compliant after reboot. Why?

We deploy patches using Configuration Manager current branch. I have some PCs that appear to have patched successfully. When I look at the deployment status, these computers are listed under "In progress" with a status of "Pending system restart"Some of these systems have been in this status for a week. I know that some of them have rebooted multiple times since the patches installed.How can I find out why the status won't update to "Success"?

:)

 

May 2018 patches cause workstation issues

We applied the May 2018 patches to the AD server (Win2012R2) and workstations (Win10) started dropping off the domain. Now workstations are patched, and cannot be pinged when they fall off, and will not stay on the
domain.

Please advise

 

HID-compliant touchscreen - optical feedback

We appreciate the information provided above. To eliminate the optical feedback that you're getting on your device, we suggest that you run these steps:

Method 1: Optimizing the pen and touch option to ensure that device is properly setup.

• Type in Control Panel on the search box.
• Press Enter.
• Click Hardware and Sound.
• Select Pen and Touch.
• Click the Touch tab.
• Remove the tick on the Show visual feedback when touching the screen box.
• Click Apply, and then OK.

Method 2: Refreshing the driver for HID-compliant touch screen to reset the driver settings.

• Press the Windows
  
  +
  X key and select Device Manager.
• Click the drop-down arrow for Human Interface Device.
• Right click HID-compliant Touch Screen and select Disable.
• Allow change to be recognized, then re-enable HID-compliant Touch Screen by repeating
  steps 1 to 3. Then, select Enable.
• Reboot the device. Select Windows
  
  ,
  locate power button, and click Restart.

Feel free to post back if you encounter any challenges along the process.

 

eDellRoot Certificate Problem: Patch Available To Fix It Now ?


Hi,

The Patch you suggested worked well, and fast.
Sure a lot easier than following 17 steps !

Any idea when the new Patch for the new problem will be available ?

Will it be posted here ? Where ?

Thanks again for all the help,
Bob