Author Topic: Many issues and a suggestion  (Read 9031 times)

0 Members and 1 Guest are viewing this topic.

Offline DanSitar

  • Newbie
  • *
  • Join Date: Oct 2015
  • Posts: 1
  • Location: Quebec, Canada
  • Karma: 0
    • View Profile
Many issues and a suggestion
« on: October 20, 2015, 11:39:03 am »
Greetings Shane, the forums' readers & helpers,  ٩̢ ̗(Ӧ̮Ӧ)̢ ̗۶

Thanks for sharing your incredible work that is so priced around the world. After having red many positive critiques,  ¿̒ ̡͡ ʅ I decided to give it a try because my laptop is really a mess โ̢ ̗(͠❂ֹ̰̃ ̰͠❂ֹ̃)̢ ̗۶‼ I am on “Windows 8 Pro with Media Center”. I made a full scan with “Registry First Aid 9.3” just before I installed your software. Here are the results:

Invalid Paths: 2125
Invalid file associations: 68
References ActiveX / COM invalid: 346
Invalid Help Files: 4
Unused software entries: 7
Uninstall invalid entries: 1657

Total: 4207
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
After all the steps of Windows Repair v3.6.1 once:

Invalid Paths: 2132 (+7)
Invalid file associations: 52 (-16)
References ActiveX / COM invalid: 346
Invalid Help Files: 4
Unused software entries: 7
Uninstall invalid entries: 1642 (-15)

Total: 4202 (-5)
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
After all the steps of Windows Repair a third time:

Invalid Paths: 2202 (+70)
Invalid file associations: 52
References ActiveX / COM invalid: 346
Invalid Help Files: 4
Unused software entries: 8 (+1)
Uninstall invalid entries: 1642

Total: 4272 (+70)

I was surprised that “Windows Repair v3.6.1” did not take care of those‼
——————————   ——————————   ——————————
Remote Access Connection
Service name: PPPoE

Something tries to connect me twice during the launch of your Windows Repair. Then, no more request after those in the Safe Mode. Sometime in Windows normal mode, I get that request even if I'm already connected with my telephone company that do not use PPPoE protocol.

Is Windows Repair trying to connect me?
Shall I delete that PPPoE stuff?

Attach: "Remote Access Connection1.png" and "Remote Access Connection2.png"
——————————   ——————————   ——————————
Step 1: Do A Proper Power Reset First!

٩̢ ̗(̾̈́͡◑̾̈́̈́͜ ̾̈́̈́͡◑̾̈́)̢ ̗۶̑ That is well explained -̀ˁ̺̍ˀ-́ . But clicking "yes" on the “Reboot Now?” doesn't give us the time to unplug the computer as recommended. It just reboot immediately. Instead, I have to click on "No", then shut it down as usual and then unplug it.

I suggest you to change it to something like:

“Safe Mode Set! Would you like to shut down, unplug for a while, then reboot?”

Attach: "Reboot Now.png"
——————————   ——————————   ——————————
Step 2: Windows Packages Files

How do I know if any of those are missing? Because 90% of the time on Windows Update, I get an Error #…
——————————   ——————————   ——————————
Step 3: After the Check Disk, right after the "View log", it is written in blue:
"No Error Found On The Drive!" But it ain't so in the log:
...
Code: [Select]
41% complete. (341144 index entries on processed 430520)
The CHKDSK.EXE-2E757381.pf index entry of $ I30 of the file 80750 is not correct.
The CHKDSK input ~ 1.PF index $ I30 of the file 80750 is not correct.
41% complete. (341 526 index entries on processed 430520)
...
——————————   ——————————   ——————————

Step 4: System file check log
C:\Windows\Logs\CBS\CBS.log

See "Cannot repair member file…", "hash mismatch…" and "do not match actual file "
Code: [Select]
2015-10-18 06:52:34, Info        CSI    000004ec [SR] Verifying 100 (0x0000000000000064) components
2015-10-18 06:52:34, Info        CSI    000004ed [SR] Beginning Verify and Repair transaction
2015-10-18 06:52:35, Info        CSI    000004ee Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:DlDsw0gnmHvb09gSf4tmlj4x7suVwNkLMYsvUZoCR6U=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-18 06:52:35, Info        CSI    000004ef [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-18 06:52:43, Info        CSI    000004f0 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:DlDsw0gnmHvb09gSf4tmlj4x7suVwNkLMYsvUZoCR6U=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-18 06:52:43, Info        CSI    000004f1 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-18 06:52:43, Info        CSI    000004f2 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
2015-10-18 06:52:43, Info        CSI    000004f3 [SR] Verify complete
Further down:
Code: [Select]
2015-10-18 07:01:11, Info        CSI    0000083b [SR] Verify complete
2015-10-18 07:01:11, Info        CSI    0000083c [SR] Repairing 3 components
2015-10-18 07:01:11, Info        CSI    0000083d [SR] Beginning Verify and Repair transaction
2015-10-18 07:01:11, Info        CSI    0000083e Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:DlDsw0gnmHvb09gSf4tmlj4x7suVwNkLMYsvUZoCR6U=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-18 07:01:11, Info        CSI    0000083f [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-18 07:01:11, Info        CSI    00000840 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:DlDsw0gnmHvb09gSf4tmlj4x7suVwNkLMYsvUZoCR6U=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-18 07:01:11, Info        CSI    00000841 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-18 07:01:11, Info        CSI    00000842 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
2015-10-18 07:01:12, Info        CSI    00000843 Hashes for file member \??\C:\Windows\SysWOW64\api-ms-win-eventing-provider-l1-1-0.dll do not match actual file [l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" :
  Found: {l:32 b:IcJ1U4cAtM9mt/SKbvZQJu9VtN+OOMqa6NrquayVO6U=} Expected: {l:32 b:rNKnpXpPwgg3J8EtpXTnlYtTAWpPm5CMw+PJiyQqZpc=}
2015-10-18 07:01:12, Info        CSI    00000844 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" from store
2015-10-18 07:01:12, Info        CSI    00000845 WARNING: File [l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" in [l:46{23}]"\??\C:\Windows\SysWOW64" switching ownership
    Old: Microsoft-Windows-MinCoreApiNamespace, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-UniversalCRT-APIfwd-Win8, Version = 6.2.9200.17488, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-10-18 07:01:12, Info        CSI    00000846 Hashes for file member \??\C:\Windows\System32\api-ms-win-eventing-provider-l1-1-0.dll do not match actual file [l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" :
  Found: {l:32 b:ydI7NDZAzD75OkUOG3y3pWkevNiGgNnuw/+Gu2J1tQ8=} Expected: {l:32 b:NtO7746IrcAynhpwUe9AC8ke91eOAKYWV822XvvoRPs=}
2015-10-18 07:01:12, Info        CSI    00000847 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" from store
2015-10-18 07:01:12, Info        CSI    00000848 WARNING: File [l:78{39}]"api-ms-win-eventing-provider-l1-1-0.dll" in [l:46{23}]"\??\C:\Windows\System32" switching ownership
    Old: Microsoft-Windows-MinCoreApiNamespace, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-UniversalCRT-APIfwd-Win8, Version = 6.2.9200.17488, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-10-18 07:01:12, Info        CSI    00000849 [SR] Repair complete

There are a lot of "[DIRSD OWNER WARNING] Directory …" and other "WARNING: File […". Should we worry about them?
——————————   ——————————   ——————————

In Repair Reparse Points

Is it possible that the "Error: 0 - Access denied" when we run the program the second time might comes from the instruction:
"Setting Owner To System And Everyone Read Access To Denied" ?

Code: [Select]
[x] RemoveDirectoryW Returned An Error, Error: 0 - Access denied.
[x] Even Though We Got An Error, Lets Keep Going.
[x] Type is JUNCTION, Calling: mklink /J "C:\Users\Administrator.Daniel-laptop\AppData\Local\Microsoft\Windows\Temporary Internet Files" "C:\Users\Administrator.Daniel-laptop\AppData\Local\Microsoft\Windows\INetCache"
[x] Setting Owner To System And Everyone Read Access To Denied (This Is The Default) To The Link Folder: C:\Users\Administrator.Daniel-laptop\AppData\Local\Microsoft\Windows\Temporary Internet Files

——————————   ——————————   ——————————

 Regards, ¿̒ ̡͡ ʅ

Daniel  ⌢ ◦ ⌢ 
 follow me on Facebook

  God bless you ‼ ≈̰ ̃(ړײ ) ̰͠


Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Many issues and a suggestion
« Reply #1 on: October 27, 2015, 08:53:48 am »
Quote
I was surprised that “Windows Repair v3.6.1” did not take care of those‼

The program is not a registry cleaner, it doesnt scan and clean the registry at all, it registers files, services and permissions and puts back regkeys for those. So dont be surprised it didnt remove those, it wasnt suppose to :-)

Quote
Something tries to connect me twice during the launch of your Windows Repair. Then, no more request after those in the Safe Mode. Sometime in Windows normal mode, I get that request even if I'm already connected with my telephone company that do not use PPPoE protocol.

Is Windows Repair trying to connect me?
Shall I delete that PPPoE stuff?

When you open my program it connects to my site to grab the update file to see if there is a new version, you can glady stop and ignore it :-)

Quote
How do I know if any of those are missing? Because 90% of the time on Windows Update, I get an Error #…
——————————   ——————————   ——————————
Step 3: After the Check Disk, right after the "View log", it is written in blue:
"No Error Found On The Drive!" But it ain't so in the log:
...
Code: [Select]

41% complete. (341144 index entries on processed 430520)
The CHKDSK.EXE-2E757381.pf index entry of $ I30 of the file 80750 is not correct.
The CHKDSK input ~ 1.PF index $ I30 of the file 80750 is not correct.
41% complete. (341 526 index entries on processed 430520)

...
——————————   ——————————   ——————————

That is chkdsk reporting that the file system isnt in good shape. You need to run a chkdsk on the drive outside of windows, you might have bad sectors or just a corrupt file system which chkdsk should be able to fix most times. If you have bad sectors then you need to replace the drive.

Open a cmd.exe window as administrator and put in

chkdsk c: /r

it will say the drive is in use and would you like to schedule it, hit Y and reboot. The scan should start before windows loads and will take a while to finish. Once it is done you can find the results in the event viewer. Post the results for me :-)

Shane