Windows 10: Driverstore file needs to be updated dptf_cpu.inf_amd64_4a on MS Surface devices due to...

HiHow do we patch this on MS Surface devices when we don't have the actual intel software that the vulnerability installed in the first place. We have noted that newer builds don't seem to include the affected file. We don't see that we should install a full intel application just to patch this. Can MS provide a patch for this?C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\ Installed version : 8.6.10401.9906 Fixed version : See vendor advisoryThis is the info from Defender..https://security.microsoft.com/intel-explorer/cves/CVE-2022-29470/description?tid=9a

:)

 

Driverstore

That day i update intel software update and fill up space to 36.5gb and now is 36.1gb and want to free up space more back to 33over gb. I know i cannot delete files inside driverfolder manually in windows folder but there's a command to check the driverstore list to see inf files which one is old or driverstore tool to also check the list of inf files. But the device driver package is still 0 bytes in disk cleanup tool.

 

Driverstore

I saw driverstore is the second big files in system 32 in spacesniffer. This driverstore folder is 3.9gb. I want to find ways how to delete old files inside driverstore. I want to see the list using dism command for driverstore in command prompt but access denied. And i saw another way to use batch file but i'm too afraid to use it might delete the whole driver. And device driver package is 0 bytes in disk cleanup tool but driverstore is a big files. And I don't know which driver is old if i use pnputil command to delete driver.

 

MS Surface Keyboard Cover not recognized by MS Surface Pro 3

My Surface Pro 3 cover mysteriously stopped working (other USB keyboards work).

I’ve exhausted all of the steps from the Internet and am hoping for some advice here on what to try next.

• Clean the metal pins on both the keyboard and the Surface Pro 3 with alcohol swap and q-tip.
  
• Performed the standard two button shutdown procedure - https://support.microsoft.com/en-us/help/4036280/surface-force-a-shut-down-and-restart-your-surface
  
• Update "HID keyboard" device in Device Manager.
  
• Uninstall and reinstall "HID keyboard device" in Device Manager.
  
• Removed HID keyboard device in Device Driver and manually installed Surface Type Cover device (which later automatically turns to "HID keyboard device" when you hit "update drivers")
  
• Updated all Windows 10 patches to date.
  
• Tried a brand new keyboard (Microsoft FMM-00001 Type Cover for Surface Pro https://www.amazon.com/gp/product/B073W4MPJF/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 )
  
• Updated firmware for Surface Pro 3 (typed in “winver”, took that Windows version, then downloaded the specific patch required here - Download Surface Pro 3 Drivers and Firmware. from Official Microsoft Download Center)
  
• Reset Surface Pro 3 while keeping personal files
  
• Reset Surface Pro 3 and deleted all personal files
  
• Performed hardware tests on aka.ms/surfacerepair (nothing bad found; all looks ok)
  
• Drained the battery most of the way before connecting again - the two times it worked momentarily these last few days was when I connected my new type cover keyboard to the Surface Pro 3 after the battery had died down to below 50%; a simple reboot later, everything stopped working. This user seems to have the same problem with it working briefly when there is low battery - https://answers.microsoft.com/en-us...pe-cover/52f983c6-2e53-49fa-aac6-7c4cc5d25d9f )
  

A breakdown of the steps I've done to sometimes get it working

• Leave Surface Pro 3 on about 2 hours on battery only.
  
• Power on Surface Pro 3.
  
• Working Keyboard.
  
• Turn off Surface Pro 3 (or reboot)
  
• Keyboard not working anymore
  
• Another similar user here - https://answers.microsoft.com/en-us...er-issue/2d6ed60a-c892-4ed9-907f-846fd9496f5a
  

Can anyone recommend any other troubleshooting steps? One of these steps seemed to work ok for others having this same problem.