Re: Error message: This app can't run on your PC,

dans AdwCleaner par fr33tux

Hello,

Hm, we'll try to get more informations:

  • Download FRST
  • Right-click on the file -> "Execute as Administrator"
  • Click on the "Scan" button
  • The logfile is saved as FRST.txt , and additional informations are in Addition.txt.
  • Please host them on Up2Share and share the generated links.

Best regards,

Re: Adwcleaner cannot remove bsdriver.sys and cherimoya.sys

dans AdwCleaner par ****

first, thank you for your advices. Here is the fixlog.txt :

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 27-07-2016
Exécuté par Charles-Etienne (2016-08-02 21:55:36) Run:1
Exécuté depuis C:\Users\Charles-Etienne\Downloads
Profils chargés: Charles-Etienne (Profils disponibles: Charles-Etienne)
Mode d'amorçage: Normal
==============================================

fixlis...

Re: ad hijacker not removed by any program - its hiding somewhere

dans AdwCleaner par fr33tux

Hello,

I don't understand if you have already used AdwCleaner or not, so if not :

  • Download AdwCleaner and make a scan with it. Then, share the generated logfile here (copy/paste it).

If you've already have:

  • Pleasehare the logfile from C:\AdwCleaner\

And:

  • Download FRST
  • Right-click on the file -> "Execute as Administrator"
  • Click on the "Scan" button
  • The logfile is saved as FRST.txt , and a...

Re: Adwcleaner cannot remove bsdriver.sys and cherimoya.sys

dans AdwCleaner par fr33tux

Hello,

We'll look deeper:

  1. Download FRST
  2. Right-click on the file -> "Execute as Administrator"
  3. Click on the "Scan" button
  4. The logfile is saved as FRST.txt , and additional informations are in Addition.txt.
  5. Please host them on Up2Share and share the generated links.

Best regards,

Re: A quand une mise à jour

dans AdwCleaner par fr33tux

Ok.

  • Téléchargez FRST depuis ce lien.
  • CLiquez-droit sur FRST.exe > Exécuter en tant qu'administrateur
  • Cliquez sur le bouton Scan.
  • Deux rapports sont alors générés : "FRST.txt" et "Additions.txt". Hébergez-les sur https://up2sha.re et copiez/collez les liens générés dans votre prochaine réponse.

Merci,

Forum Software Developer Needs Hosting Space..

dans ToolsLib par KYHI

Hello All,

I have several large Windows Rescue Disks that run in a Windows PE enviroment..

These ISO's are about 1GB in size and I average about 200 downloads per day for the last 6 months..

I also create other scripts, tools or utilities that are smaller programs, but also with a high download amount..

I have uploaded several of the smaller programs here and I am awaiting approval...

Thes...

Re: Bug report for QuickDiag

Hello!

Great news! Finally, I can now confirm that QuickDiag works perfectly, from start to finish, and without error messages! Yay!

Just before QuickDiag finished, I got a popup asking me if I would let QuickDiag communicate on my local network through the Windows Firewall; I answered Yes, and the program finished with creating its log file on my Desktop.

So, once again;

Thank you for Quic...

Re: Bug report for QuickDiag

Hello!

Thank you for updating QuickDiag, however the same error still persists.

Both of these files belong to the backup and disk imaging program Acronis True Image 2016.

It is a comprehensive program with a ton of features, and therefore its files take up the biggest amount of disk space of all my software.

Please let me know what more I can do to help.

Regards,

midimusicman79

Re: Bug report for QuickDiag

Hello!

Thank you for updating QuickDiag!

The signers of these files are as follows:

aaf275.msi -- Acronis International GmbH and Symantec Class 3 SHA256 Code Signing CA

ab11370.msi -- Acronis International GmbH and Symantec Class 3 SHA256 Code Signing CA

Thank you!

Regards,

midimusicman79

Re: Bug report for QuickDiag

Hello!

Thank you for fixing the bug and updating QuickDiag; I can confirm that it does jump over the corrupted files, however now QuickDiag hangs at another file: C:\Windows\Installer\a0884cd.msi

This is the error message: "Error allocating memory".

Following the pattern from before, the actual error files would be these: C:\Windows\Installer\aaf275.msi and ab11370.msi

 

Here is the log ex...