can not open Devices and printer PLANK

There's not much corruption as such - just the one file...

Code:

 Line 20011: 2015-06-08 17:54:13, Info                  CSI    00000344 [SR] Repairing 2 components
 Line 20012: 2015-06-08 17:54:13, Info                  CSI    00000345 [SR] Beginning Verify and Repair transaction
 Line 20015: 2015-06-08 17:54:13, Info                  CSI    00000347 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 20018: 2015-06-08 17:54:13, Info                  CSI    00000349 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 20021: 2015-06-08 17:54:13, Info                  CSI    0000034b [SR] Cannot repair member file [l:28{14}]"iscsi_init.CHM" of Server-Help-CHM.iscsi_init.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

The other two unrepairable files are 'by design' - i.e. a bug that MS may or may not get around to fixing this side of EOL
You can get rid of those by uninstalling KB3022345 or KB3068708 (or both), and hiding them/it whe the reappear in the update list.


I'll post a fix for the remaining file soon.

I've uploaded a file - m2naa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\m2naa
hit the enter key - if you get a 'Not Found' error try
DIR D:\m2naa
or
DIR E:\m2naa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\m2naa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

- error say regsv32.exe unable to start correctly

Unless you meant to type 'regsvr32.exe' then that file doesn't exist in Windows.

Please ZIP/Compress the CBS.log file - I'm on a metered connection!

Thanks - the error is still present

Code:

 Line 769908: 2015-06-10 12:18:18, Info                  CSI    000004fd [SR] Repairing 1 components
 Line 769909: 2015-06-10 12:18:18, Info                  CSI    000004fe [SR] Beginning Verify and Repair transaction
 Line 769912: 2015-06-10 12:18:19, Info                  CSI    00000500 [SR] Cannot repair member file [l:28{14}]"iscsi_init.CHM" of Server-Help-CHM.iscsi_init.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

It's too late now, but I'll review and try again tomorrow.