Desktop window error:
"Unable to execute a file from the temporary folder.
Installation aborted.
"Error 4551: An application control policy blocked this file.
Windows security notification:
"Part of this application has been blocked.
Some features of the Hasleo Backup Suite installer may not work because we cannot confirm the publisher of DB1A337C-XXXXX-XXXXX-XXXXX-XXXX.tmp (the alphanumeric string changes with each update attempt)."
I disabled Smart App Control to perform the update and re-enabled it afterward. Everything seems to be working fine now.
I'm just mentioning this in case the problem is with the Hasleo app and not Smart App Control.
Lost my SSD and had to reload all software and now Backup suite tells me the license key I
have has exceeded the number of activations allowed.
How can I fix this?
Bill
I'm trying to use Hasleo Data Recovery Home Edition to recover some deleted files and folders from my SSD. After the "Deep Scan Recovery" finishes, I select the files I want to recover, obviously to a different storage drive since my Windows is on C: and I have another SSD installed as D:. When I hit Recover, Hasleo Data Recovery asks me to enter the license code, and as soon as I do, the software just closes on its own.
I've tried this at least 5 times now, and the software keeps closing itself and never actually recovers the files/folders.
Does anyone know if this is a common issue? Could it be something I'm doing wrong during the recovery process? Does it have to do with the number of files being recovered? Could it be related to the file size (they don't add up to more than 1GB total)?
I'd really appreciate help from support or from anyone who's dealt with this before, because the files I need to recover are important — they're files and folders deleted from the .codex folder, which sits in the system's user folder, and it has structured projects, chats, and history in it.
I've attached some screenshots showing that right after I select the folders and files, Hasleo Data Recovery asks for the license code again. When "Activation Successful" pops up, the software just closes on its own.
Olá a todos, enviei um e-mail com as capturas de tela e links necessários mostrando meus compartilhamentos do Facebook e do X (Twitter) para solicitar a licença de 1 ano do Hasleo Data Recovery Home, juntamente com uma breve descrição de seus recursos e benefícios.
Alguém sabe qual é o tempo médio de resposta do suporte da Hasleo por e-mail? qualquer pedido de informação!
Mudando de assunto, eu não conhecia o Hasleo Backup Suite até recentemente, então gostaria de saber como ele difere do Hasleo Data Recovery e quais são os principais benefícios que o Backup Suite oferece.
Para contextualizar, sou apenas um usuário comum que trabalha com muitos arquivos grandes, desenvolve aplicativos e está constantemente atualizando o Windows e tentando manter o sistema seguro. As ferramentas Hasleo têm sido de grande ajuda para isso, puramente para uso pessoal - nada relacionado a empresas ou equipes.
--- English ---
Hello everyone, I sent an email with the necessary screenshots and links showing my Facebook and X (Twitter) posts to request a 1-year license for Hasleo Data Recovery Home, along with a brief description of its features and benefits.
Does anyone know what the average response time is for Hasleo’s email support? Any information would be appreciated!
On a different note, I wasn’t familiar with Hasleo Backup Suite until recently, so I’d like to know how it differs from Hasleo Data Recovery and what the main benefits of the Backup Suite are.
To provide some context, I’m just an ordinary user who works with many large files, develops applications, and is constantly updating Windows and trying to keep the system secure. The Hasleo tools have been a great help with this, purely for personal use—nothing related to businesses or teams.
So I just started using Hasleo and got some great help from people in another thread about setting up retention. However, now I've got a real weird issue.
I started a test backup and it was going but quite slowly and I wanted to restart my PC for something else anyway so I stopped the backup to do that. Before rebooting, I also uninstall Macrium Reflect X, which I was using prior.
Now after rebooting, I can't start my backup job or save a new one. I get the error "Network failure, please make sure network works properly and try again. (0x00CF00D200000533)"
Thing is, my network is fine. I can reach the file share in other applications and it even comes up when I browse to the folder from the backup job creation screen. I tried uninstalling and reinstalling Hasleo in case removing Reflect X messed up some shared component or something but nothing's changed. I'm a bit baffled by this error since the problem it's mentioning isn't otherwise a problem.
I've attached a Zip with everything from the logs folder. Does anyone potentially see what the issue is?
I hadn't used my SanDisk Extreme Pro 128 GB flash drive—which runs Windows 10 Live—for quite a few months. When I plugged it in, Windows 10 naturally prompted me to install updates, so I did. After the required restart, however, Windows 10 Live wouldn't load; the Windows logo appeared on the screen but remained frozen. I performed a hard shutdown, turned it back on after a minute, and encountered the same problem. That was when I learned that after two or three hard shutdowns, a screen offering startup assistance or repair options should appear.
That screen did appear, but it froze as well. I performed another hard shutdown, and a blue screen appeared with a message like "preparing for repair" or something similar. Once again, everything stalled. I waited hopefully for half an hour but eventually had to turn off the computer.
Is the Windows 10 Live installation irreparably broken? Is there anything else I can do?
I'm a Macrium Reflect v8 refugee who is finally trying alternatives after I tried to mount a backup last night and found out Macrium's driver for that has been blacklisted by Microsoft for a CVE and their answer is "upgrade to the subscription version".
When using Reflect, I had what's often called a Forever Forward Incremental backup policy. It took a full backup at the start, 7 incrementals and then once it took the next one, the oldest incremental would merge back into the full. Given that the backup I take is almost 8TB before compression and doesn't have huge daily changes, I found this method to be quicker than taking a fresh full every week.
The renention policy settings screen in Hasleo and the web documentation doesn't make it clear to me how I achieve this here. From what I've read elsewhere, it is possible but I can't find the right combination of settings. I can specify for it to keep 1 week of Fulls and 7 days of Incrementals but from what I'm reading, that will take another Full at the end of the week instead of merging the oldest Incrementals. I looked into the "Always retain the first backup" setting which is recommended for both users but from what I read on that, it will just keep the first backup untouchable, meaning it won't do any merging at all.
I'm sure what I'm asking is possible and I just don't understand the different way Hasleo does setting versus Macrium. Can anyone clarify what I'd need to set this up?
There are posts, articles, and FAQs on why backups should be made, and how to do restores.
I made good use these processes over the last couple of days.
My first set was performed on a test PC as part of an informal benchmark (results posted here in another thread). In total there were:
- one full System backup (regular Tue pre WU)
- 4 System backups performed by HBS and other
- 4 System restores by HBS and other (~ 2 minutes per)
This was followed by restore of the full System backup to wipe all traces of the other test product install.
The next set was part of a process to get a current V5.9.2.1 winpe.iso built on a stable Win 11 system (26200.8737) that works for my laptop.
- make a full System backup (regular Tue pre WU)
- restore an INC backup prior to the July 14 WU when the problems started.
- build and test a winpe, found that it has issues
- restore the previous INC backup
- build and test a new winpe, this one worked so it was saved.
- restore the full System backup
- move the saved winpe to HSB\bin, then setup Boot Menu & ED
Then business as usual on both PC's without any issues. Good job HBS.