silverfern
Contributor
- Sep 12, 2016
- 6
Hi,
I encountered problems with a service: Secure Socket Tunneling Service, it does not start and I need it for my VPN client. So after searches i stumbled over the SFC tool.
So I executed scannow option
So CBS log found:
Some searches brought me over to this forum, and found some threadsI downloaded the SFCfix and the zip an executed it. But it hasn't helped yet.
I also tried to restore health with DISM tool:
Attached logs:
Am I doing something wrong? If anyone could help me with that. If it is a double post, please delete my post and point me to the right one, thanks
I am using Windows 8.1 Pro.
Many thanks
Silverfern
P.S. I am aware that this maybe won't fix my VPN, but eliminates an error source.
I encountered problems with a service: Secure Socket Tunneling Service, it does not start and I need it for my VPN client. So after searches i stumbled over the SFC tool.
So I executed scannow option
Code:
C:\Windows\system32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
So CBS log found:
Code:
(p) CSI Payload Corrupt amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB
Repair failed: Missing replacement payload.
Some searches brought me over to this forum, and found some threadsI downloaded the SFCfix and the zip an executed it. But it hasn't helped yet.
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-13 13:00:25.797
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\<username>\Desktop\SFCFix.zip [6]
PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log
WARNING: File C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log was not backed up as that would replace the current backup.
Successfully copied file C:\Users\<username>\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log to C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log.
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.log
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-09-13 13:00:25.938
Script hash: FwjWZEfnDUiFWdpCcZd8iBkeSZ/4MDtSavZbCwhsPnQ=
----------------------EOF-----------------------
I also tried to restore health with DISM tool:
Code:
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\sources\install.wim:1
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http
://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Attached logs:
Am I doing something wrong? If anyone could help me with that. If it is a double post, please delete my post and point me to the right one, thanks
I am using Windows 8.1 Pro.
Many thanks
Silverfern
P.S. I am aware that this maybe won't fix my VPN, but eliminates an error source.