Tweaking.com Support Forums

Main Forum => General Computer Support => Topic started by: whiggs on August 11, 2015, 12:57:18 pm

Title: potential bug windows all-in-one repair?
Post by: whiggs on August 11, 2015, 12:57:18 pm
Hey all,
Didn't see a "bug report" section in the forum, but I wanted the creator of Windows all-in-one repair aware of what I believe to be a potential bug when using the software on windows 10 64-bit.   There are two images attached:
error.jpg shows the results of a reparse point scan for errors
total.jpg shows all reparse points detected by the program.
I have run the program as indicated on Welcome screen: in safe mode as an administrator (I am using the administrator account which I activated), yet Windows AIN repair will not fix the supposed reparse point errors.  To clarify, I select repair, run the scan again, and the same three reparse points just re-appear again and again.  Furthermore, I had noticed in prior operating systems that the command prompt will pop up for every repair being made.  That does not occur in Windows 10 64 bit when the reparse points are being repaired.  Just wanted to improve the progrm, so do with info what you will.  Thanks for the awesome piece of software.
Title: Re: potential bug windows all-in-one repair?
Post by: Shane on August 11, 2015, 01:00:16 pm
Just had another user let me know
http://www.tweaking.com/forums/index.php/topic,3482.0.html

I am fixing it right now and is an easy fix, While I plan on having an update out next week i might do it sooner so I dont get flooded with users thinking their points are bad lol

Shane
Title: Re: potential bug windows all-in-one repair?
Post by: Tacotardis42 on August 11, 2015, 06:02:40 pm
Yes, please do because I was having a very similar problem on 7, and I was literally about to post it.
Title: Re: potential bug windows all-in-one repair?
Post by: Shane on August 12, 2015, 06:37:14 am
I posted in the other thread a test build I spent all night working on, if you want to test it out for me and report back before I release it later today :-)

Shane