Jump to content
CCleaner Community Forums
Eli

Auslogics

Recommended Posts

Hi

 

Yesterday I defragged + optimized the system with Auslogics disk defrag , after reboot ,system turned to a cold stone ,although able to reboot, nothing was operable, fortunately had the system restore on .

Question: Did any of you encounter such an incident ?

 

Thanks

Share this post


Link to post
Share on other sites

Hi Eli.

 

I use Auslogics, mostly to compare the displayed results of Defraggler, and sometimes the other way around.

 

I've never had an issue, although I've only just noticed there's a newer version to mine, and I have never used the "Defrag and Optimize" setting. In fact I never use the "Optimize" setting with any defragger.

 

Not much more I can say really. It's always been OK for me (XP) with a basic defrag, and I can't find much regarding issues with a google search either.

Share this post


Link to post
Share on other sites

Hi Eli.

 

I use Auslogics, mostly to compare the displayed results of Defraggler, and sometimes the other way around.

 

I've never had an issue, although I've only just noticed there's a newer version to mine, and I have never used the "Defrag and Optimize" setting. In fact I never use the "Optimize" setting with any defragger.

 

Not much more I can say really. It's always been OK for me (XP) with a basic defrag, and I can't find much regarding issues with a google search either.

Thank you Dennis I guess it was a sort of coincidence.I`m waiting for Auslogic`s support team regarding this matter.

Share this post


Link to post
Share on other sites

I have the "move system files to the beginning of the disk" option checked under Algorithms and run the "defrag & optimize" option once a week. I've never had a problem.

Share this post


Link to post
Share on other sites

I have the "move system files to the beginning of the disk" option checked under Algorithms and run the "defrag & optimize" option once a week. I've never had a problem.

I have the same settings as yours + skip files larger than 50 MB, and this is the first time it happened after a year of use.

Share this post


Link to post
Share on other sites

Do you occasionally run Check Disk ("chkdsk") in Windows though? Some say "never use it," but if you're defragging often it can't hurt to use it once per week, as there has to be a very good reason even Windows Disk Defragmenter won't run if ChkDsk is scheduled on the next boot.

Share this post


Link to post
Share on other sites

Do you occasionally run Check Disk ("chkdsk") in Windows though? Some say "never use it," but if you're defragging often it can't hurt to use it once per week, as there has to be a very good reason even Windows Disk Defragmenter won't run if ChkDsk is scheduled on the next boot.

I occasionally do run chdsk once in a while and it wasn`t scheduled when it happened.

Share this post


Link to post
Share on other sites
I occasionally do run chdsk once in a while and it wasn`t scheduled when it happened.

What settings are you using so that it doesn't run in read-only mode? I've tried running "chkdsk /f" and then hitting "Y", but it never seems to run at the next boot.

Share this post


Link to post
Share on other sites

What settings are you using so that it doesn't run in read-only mode? I've tried running "chkdsk /f" and then hitting "Y", but it never seems to run at the next boot.

Never used Auslogics to chkdsk I always use WINDOWS chkdsk

Share this post


Link to post
Share on other sites
Never used Auslogics to chkdsk I always use WINDOWS chkdsk

Yeah, me either. I was talking about Windows chkdsk. I've only gotten it to run in "read-only" mode.

Share this post


Link to post
Share on other sites

Yeah, me either. I was talking about Windows chkdsk. I've only gotten it to run in "read-only" mode.

Did you try to chkdsk with auslogics or defraggler to see if it works next boot? if did not work either ways maybe you have got some security application avoiding that operation.

Share this post


Link to post
Share on other sites

It's possible that security apps are interfering with chkdsk.exe because they're locking the drive before it has a chance to run.

You could get around this by using Hiren's Mini XP and running chkdsk.exe from the DOS Prompt "chkdsk c: /f" (do not "c:" "chkdsk /f").

Alternatively you could just run "chkdsk.exe /f" but reboot your machine and start Windows in Safe Mode.

During Safe Mode you will see all the driver files loaded by Windows but nothing appears to be happening after that apart from a lot of disk activity.

In actual fact it's chkdsk.exe running in the background but for some reason it doesn't display anything on the screen while working.

Once done it should reboot the computer and start in normal mode (unless Windows is installed on a fat32 partition).

To check the chkdsk report, run Event Viewer (eventvwr) and open Application, event "Winlogon"

 

Richard S.

Share this post


Link to post
Share on other sites
Did you try to chkdsk with auslogics or defraggler to see if it works next boot? if did not work either ways maybe you have got some security application avoiding that operation.

I didn't realize until you said that that Auslogics included that functionality, but yes it is working fine now.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...