Solved sfc /scannow finding corrupt files but can't repair them

[Petra654]

Here you go...

 

[NoelDP]

Hmmm - Repair Environment should see Windows in the D:drive ??

 

[Petra654]

Actualy, Windows is installed in C:drive.

 

[NoelDP]

The Repair Environment re-enumerates the drives sequentially, and not according to the same sequence as the normal Windows install - that's why we have to search for it when we need to do this kind of thing.

 

[Petra654]

Soo, I should go again in the Repair Environment-Cmd and go "DIR D:\skcaa" (or search for it if it isn't od D?

 

[NoelDP]

Yep - it should be in the D: drive, though. If you don't see it, try DIR D:\Windows - what does that show?

 

[Petra654]

Same thing, "FileNot Found".

 

[NoelDP]

Very odd.
OK - we'll try to do the file replacements another way, then.

Please download SFCFix from here... http://www.sysnative.com/niemiro/apps/SFCFix.exe and save it to your desktop (we'll need it later anyhow, I think)

Once saved, double-click on it and accept the warnings. It'll run, and create a file SFCFix.log on the desktop - please upload it to your reply.

 

[Petra654]

Here you go:

 

[wben353]

Windows 7 x64 aio (All In One)

Sorry the link took so long, had issues with file size. Here's the link to the file on my Google Drive account CLICK HERE. If you need permission, click on it and I'll provide same. Good luck with your computer woes.

Bill

 

[Petra654]

Okey, I asked for permission. Thank you.

 

[NoelDP]

Here you go:

Well, we got 2/3 of the way there!

AutoAnalysis::
SFC verification failure on file sppcomapi.dll of component Microsoft-Windows-Security-SPP-UX (amd64, version 6.1.7600.16385). Permissions may be damaged - attempting automatic repair.
Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7600.16385_none_b7b69062b883381f\Security-SPP-UX-ppdlic.xrm-ms and all associated hardlinks.
Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7600.16385_none_b7b69062b883381f\slui.exe and all associated hardlinks.
Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7600.16385_none_b7b69062b883381f\sppcomapi.dll and all associated hardlinks.
Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7600.16385_none_b7b69062b883381f\sppcommdlg.dll and all associated hardlinks.
Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_6.1.7600.16385_none_b7b69062b883381f\sppuinotify.dll and all associated hardlinks.

FIXED: Corruption at C:\Windows\winsxs\amd64_prnle003.inf_31bf3856ad364e35_6.1.7600.16385_none_3bd93998e623907a\prnle003.inf has been successfully repaired from C:\Windows\inf\prnle003.inf.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-b..core-fonts-kor-boot_31bf3856ad364e35_6.1.7600.16385_none_b6bc71f2aed192c1\kor_boot.ttf has been successfully repaired from E:\Windows10\boot\fonts\kor_boot.ttf.


CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-shell-acccursors_31bf3856ad364e35_6.1.7600.16385_none_406675269603c3b4\wait_il.cur

The error s there beg the question of why you haven't mentioned the system showing as non-genuine!

I need to see a full copy of the report produced by the MGADiag tool
(download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.

 

[Petra654]

I had entered a serial on install i got with this windows, and today i saw that the serial got blocked...when the post was posted it was genuine, well, it said it was... but no matter now... here you go:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-TQGX8-C8B9B-BGXFF
Windows Product Key Hash: zwm29/2Er/jco/UzoZnol3s8ds4=
Windows Product ID: 00426-065-1031097-86875
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7600.2.00010100.0.0.001
ID: {00025D02-0BF3-4B80-BD08-6A65AF5162AC}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7600.win7_gdr.150318-1623
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Standard 2007 - 103 Blocked VLK
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{00025D02-0BF3-4B80-BD08-6A65AF5162AC}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-BGXFF</PKey><PID>00426-065-1031097-86875</PID><PIDType>5</PIDType><SID>S-1-5-21-3563071749-254414002-739170843</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P67-DS3-B3</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F1</Version><SMBIOSVersion major="2" minor="4"/><Date>20110506000000.000000+000</Date></BIOS><HWID>63B83607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0012-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>84B9C24ED082586</Val><Hash>tyiZ/dcb+zqWe0jHG65uncl8TX8=</Hash><Pid>89396-707-0366501-65554</Pid><PidType>14</PidType></Product></Products><Applications><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/></Applications></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Input Error: Can not find script file "C:\Windows\system32\slmgr.vbs".

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MgAAAAEABAABAAEAAQABAAAAAQABAAEA6GG07AJTPkJyOGI0St3eJb7pGoDOmhZ/LnM=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC GBT GBTUACPI
FACP GBT GBTUACPI
HPET GBT GBTUACPI
MCFG GBT GBTUACPI
ASPT GBT PerfTune
SSPT GBT SsptHead
EUDS GBT
TAMG GBT GBT B0
SSDT INTEL PPM RCM
MATS MATS RCM

 

[NoelDP]

Apart from the fact that there is an Activation Exploit present....
...and Office is counterfeit....

The Key in use is an MSDN Key from a not-for-resale MSDN account.
Unless you are an MSDN subscriber, you are not entitled to use the Key – and whoever sold it to you was not entitled to do so.
You need to claim an immediate refund from the vendor - do NOT accept the offer of a new key (all they are trying to do is to get past the 45-day claims window or avoid you sending the evidence of their crimes to the authorities)

Please read the following posts.... .................................

Blocked Product Keys

and

Advice on Safe Software Shopping (revised 4/10/2011)

The pirates have got VERY good at this over the past few years, as the price of equipment for manufacturing the packages drops, and as factories open in less well-policed countries.

see also this post....

The New York Times - Chasing Pirates: Inside Microsoft’s War Room


Also - have a look at this video....


Bogus Windows 7 warning - YouTube

You may be able to get a complimentary copy of the OS from Microsoft - fill in the Counterfeit report here...
How to Tell - Home

 

[Petra654]

Okey, thank you.