Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: rvail317 on July 19, 2016, 09:20:31 am
-
Don't know whether this problem is related to this one:
http://www.tweaking.com/forums/index.php/topic,134.0.html
But with the most recent tweaking.com utility 3.95 version, the "Repair Reparse Points" function fails to make any repairs.
This is for the latest Win10 64-bit, "Insider" build 14393.
The tweaking.com utility 3.95 finds 28 Reparse Points needing repair ("Problems Found: Yes"), but although the Repair function seems to churn away for a minute or two, nothing actually gets repaired. I've also tried booting into Safe Mode, with the same result.
Note: this particular O.S. installation has been re-updated several times from a previous "Insider" build, so maybe a complete re-format and re-install would clear up the errors.
-
It did not do anything for me too and not on the insider bu.ild.
-
I've already opened this thread for a Win 7 system -
http://www.tweaking.com/forums/index.php/topic,4745.0.html
-
Maybe we should combine the two so there is only one thread on this topic.
-
I haven't tried that yet as I didn't want to screw things up, :) but I've already emailed Shane with links to both my WR problem threads but as yet there hasn't been a response.
I'll give him another nudge and just link this one which contains mine as well.
-
Shane is unable to replicate it in Win 10 so can you run the Pre-Scan and repairs again then post the log as I have, so Shane can try to see what is going wrong.
-
Log attached; appears practically identical to yours.
-
Log attached; appears practically identical to yours.
I've since upgraded that machine from Win 7 to Win 10 and a Pre-Scan found 52 Reparse Points this time but after running the repair, that came back clean.
Shane made some adjustments to 3.9.5 for a Permissions problem, so can you download the program again, run the Pre-Scan then go to the Reparse repair window, run the scan but without running the repairs and post a PRTSC of that and I'll send Shane a link to your thread with that attached.
That is what he was wanting me to do with mine, but I no longer have the problem.
-
OK: re-downloaded the tweaking.com v. 3.95 program, attempted repairs to Reparse Points & Environmental variable, but unable to fix either.
Log file & PRTSC attached.
-
Thanks - I'll email Shane with a link to this thread.
-
Shane thinks it could be because it's an Insider and not a public build and you can leave the Pre-Scan on that - or you getting any problems because of them ?
-
Note: Windows 10 Build 14393.3 is (reportedly) the final RTM build, scheduled for release on Aug.2.
First noticed Reparse Point errors on Win 10 several builds previous.
Was hoping that updating to a newer Win 10 build number would have repaired the Reparse Points error, but unfortunately did not.
What prompted the diagnosis attempt, was that a certain older program needed Dot NET 3.5, which was balking when using the normal installation procedure.
Dot NET 3.5 is an optional feature that can be installed on an as-needed basis from the Win10 installation media.
-
.NET Framework 3.5 is part of Windows.
Go Start - type appwiz.cpl and press enter - click on Turn Windows features on or off and when the window populates, you should see an entry for 3.5 with a filled box.
This means that only part of it used.
If it isn't filled then click on it - OK and see if that is the cause of the Reparse Point problem.
If it is filled then click on it to uncheck - OK - you could try a reboot then go back and re-check its box.
-
.NET Framework 3.5 is part of Windows.
Go Start - type appwiz.cpl and press enter - click on Turn Windows features on or off and when the window populates, you should see an entry for 3.5 with a filled box.
This means that only part of it used.
If it isn't filled then click on it - OK and see if that is the cause of the Reparse Point problem.
If it is filled then click on it to uncheck - OK - you could try a reboot then go back and re-check its box.
Yes, but what are you supposed to do when that fails to work properly?
What did work for me was:
Command Prompt (Admin):
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:z:\sources\sxs
Where "z" is the drive letter of the USB thumb drive (or optical disk) used for the O.S. installation.
-
Nice find - do you have a link to that fix ?
Does WR still find Reparse Points to fix and unable to repair them ?
-
Nice find - do you have a link to that fix ?
Does WR still find Reparse Points to fix and unable to repair them ?
1. Second reply here: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/how-to-instal-net-framework-35-on-windows-10/450b3ba6-4d19-45ae-840e-78519f36d7a4?auth=1
2. Yes, same Reparse Points errors & unable to repair. No noticeable bad effect of having the errors, however.
-
Perhaps the 2nd Aug. update will help.
Do you intend to actually upgrade or just stay with the Insider TP ?
-
Same problem here with Windows 10 Pro x64 Build 14393 and build 10586. Worked before version 3.9.5
Error reparse points never go away. Reparse points are never fixed. Tried re-running app, as admin, and still finds all reparse points. Doesn't seem to fix them anymore.
Ran on multiple systems, same problem. Bug in program.
-
I've emailed Shane, adding your post to the list.
Not sure when I'll get a reply as he'll have to check the program, but I don't think he found anything first time around.
Will update when I get a reply.
-
I may as well add mine here as well.
Just run the Pre-Scan on a recently Win 10 upgraded laptop and it found 72 Reparse Points to fix.
Ran the repair and another scan and it found the same ones.
Attached is what it said during the repair and a screen shot of what it failed to repair.
-
New version 3.97 posted today: same result.
-
Are you all running 1586.494 or has anyone upgraded to 1607 with the Anniversary Update yet.
Shane has done that on one of his machines and is checking the reparse points out - waiting for an update on that.
-
Don't confuse version number vs. build number.
Version 1607's latest build number is 14393.10.
At a command prompt, type "winver".
-
Same problem here (see attached files). Win 10 Pro Version 1511 Build 10586.494 (64-bit). Tweaking.com repair v3.97 Pro. Reparse Point repair worked well in the past. This is the first time I'm using the repair program after an In-Place update to the Win version above. Hope Shane would be able to solve the problem soon, but I'm not too worry since CHKDSK and SFC scans are OK.
Ron
-
Don't confuse version number vs. build number.
Version 1607's latest build number is 14393.10.
At a command prompt, type "winver".
I haven't been able to upgrade mine yet so I can only go on the version number and I know about winver.
-
While waiting on a fix, here's an interesting/useful "Dism++" software that includes some useful functions:
https://www.chuyu.me/
It can (safely) clean out WinSxs stores, which saved ~600 Mb to ~1,200 Mb on various machines, can disable the little arrows on desktop icons, and dozens of other tweaks.
Can also convert .esd files to .iso files.
Download links for Win 10:
https://twitter.com/WZorNET
-
Shane has incorporated a fix in 3.9.8 but I've found that while it will report no problems with Reparse Points after running the repair, it still lists them as info at the bottom of the repair window.
I've emailed him about that, so will have to wait until he checks that out.
-
Build 3.9.9 was released quickly after 3.9.8.
No reparse errors now being reported, build 14393.10.
-
I'll have to update and see how that reports mine.
I had let Shane know how 3.9.8 was reporting on mine and not fully opening in Safe Mode when not connected to the 'net.
-
I've run 3.9.9 and it's doing the same as 3.9.8
The Pre-Scan says no Reparse Point Problems but underneath it says it has found 73 and when you hit the repair button and it does the scan, nothing comes up with it saying at the bottom, Problems: No but for Info it reports 73.
It's as if it's ignoring non-system Reparse Point corruption.
There doesn't appear to be any adverse effects, but it makes you wonder what is wrong with the ones it reported previously.