Problems scheduled blue screen tasks with Backupper
Could it be more accurate when this problem will be fixed? I want to buy the program, but with all this delay it gets complicated.
Is there any way to pass an exact date?
Is there any way to pass an exact date?
Comments
What system are you using? Are you using AOMEI Backupper Standard Edition?
As for the problem, we have a fixed edition for win10 system. Please try it.
AOMEIBackupperStd.exe:https://drive.google.com/file/d/1Ns3vvcqTBgxnQGBaKdFdTPdnh3Dtdw5p/view?usp=drivesdk
Please first uninstall AOMEI Backupper you have installed via Control Panel, then delete ambakdrv.sys, ammntdrv.sys, amwrtdrv.sys under C:\Windows\System32, reboot the computer, install the new version we sent.
Example date: 05/08/2020, 10/08/2020, etc...
I see users saying that they change the drive of the normal version for this version of the link. It's been almost a year and nothing.
It took me since signing up here a almost one year ago till last night to finally get your system to send my confirmation email so I could make a post/reply (I did read you had issues but this was a year ago).
I installed the "Fixed" 5.8 but it could not see the System Partition for some reason even though the older 5.8 could so I sat and waited and waited till last night the email arrived and today you offered 5.9.
I set it all up and BOOM, a nice big BSOD and on restarting all my settings were erased (lucky I had backed up the config) so I loaded it back in and rescheduled and let it run gain and once again BSOD and all setting erased.
I am going to give up on this and use the built in Windows one as it works and it is safer on my SSD/HDD's getting powered down like that.
I now as of today's 2x BSOD have a few Desktop Gadget corrupted that I cannot get to fix without a clean Windows 10 install but no way I am doing at this time.
EDIT: no was not the above causing issue due to upgrade as still the same in new set up in 5.9 so can assume with these new Sync settings choices it is broken.
I put some files as a test in a folder I am Syncing to a external HDD, they are copied to the external HDD that is working as intended but then I delete the source files and they do not get removed from the external HDD.
I should just go back to MS Sync Toy as it still works in Win10.
As for the sync, did you create common sync via the old version? or real-time sync? For the original common sync of the old version, it will not delete the files from the destination when they are deleted from the source. Only real-time sync can sync the deleted files. Of course, the sync features of v5.9 supports the feature. Please try to use v5.9 to create the sync task and check again.
"I now as of today's 2x BSOD have a few Desktop Gadget corrupted that I cannot get to fix without a clean Windows 10 install but no way I am doing at this time."----What is Desktop Gadget? Did you mean that a few Desktop Gadget are corrupted after the backup BSOD and reboot? And, what status are these Desktop Gadget? Could you give us a detailed description?
It was working till I updated to 5.9 the other day and I assumed it may have stopped working due to the new multiple Sync options in 5.9 so I Deleted/Cleared History/Rebooted PC and set it up again as Real Time Sync but its not working correctly.
I will need try and fix that another day but for now need my Syncing working which is totally newly set up to Real Time in 5.9 as it did on previous builds.
So I ran another test with it re-enabled and opened the Windows Task Manager which shows the HDD is constantly being written to at around 140MB/s by AOMEI so my internal Storage SSD is continually being read to it.
I have had to delete the Sync for now.
The ABsync program is for real time sync. Generally, when the real-time sync is syncing data, it will continually read and write the source and target drive. When sync is completed, the ABsync program will still keep running to monitor the change of the source. Once there are any changes in the source, it will sync any changes or newly created files to the destination folder immediately.
So, when you set the real-time sync task, the ABsync can't remove. And, if the ABsync program is continually reading and writing the source and target drive, the real-time task is syncing data.
Once the files are synced initially and no new ones added it should not read from my SSD to my ext HDD at full speed forever.
I assume you know ever time I update this program it goes though the sync process even though the file are already on the destination HDD.
Could you try to recreate the real time sync task via v5.9, and then check if you will get the problem again?
I never used this setting before but the description make it sound handy as if I delete a file from the Destination Drive by error it will be re-written where as normally it will not.
As soon as I Edited/Unchecked this is stopped but returned on next PC Restart so I deleted the
Sync Task , rebooted and set up a new Sync Task without that setting for now.
To undo it I Edited the Sync Task again and unchecked the box and rebooted which this time did stop the issue without deleting the Sync Task and setting up a new Sync Task.
Could you allow us to offer remote assistance for the problem? If yes, please contact us via email so that we appoint a suitable time to connect the remote. Is It ok?
There is nothing you can do that I cannot do myself and if you want me to try something then instruct me but I really do not want my PC running slower at times with HDD's thrashing for hours.
I will do without that setting for now as I never used in past but the BSOD issue with the schedule is over one year old now and has nothing to do with Win 10 2004 build
It will take while but I do not epect it to hammer my HDD on every Restart, even though neither are my OS drive its lags PC at times probably due to CPU use on 200-300+MB/s transfers.
I will post back later.
And, when there are some changed files, the real-time will sync them. After syncing these files, the sync will scan and check all files again to see if there are missing files that failed to be synced.