Hi :)
studying your files gave me an idea (reading the offstes) and it helped me and now the bug is fixed and I thank you again
henceforth QuickDiag will jump over the corrupted files
Regards :)
Hi :)
studying your files gave me an idea (reading the offstes) and it helped me and now the bug is fixed and I thank you again
henceforth QuickDiag will jump over the corrupted files
Regards :)
Hello thanks ;)
the files are , like I thougt , exactly the same.
the content of them is 10 280 Ko of zeros , just full of empty space , nothing else :D
Regards :)
Happy for you :)
if you move them in another folder you'll be able to finish the diag in a good way :) ( quickdiag analyses the msi files only in this folder ( Installer ) , you can for example create a folder in C:\Windows\Installer with the name you want and put these files to keep them not so far and do again a scan with quickdiag , I think it'll go 'till the end :)
sorry for my english bu...
Hello!
Thank you for studying them, and for confirming that the problem lies in the file named 5f6db.msi itself and not QuickDiag.
As it happens, I also have another file named 9acb635.msi, which is equal in date/time, size and MD5, which also is corrupt.
[2015.05.08 07.17.50 | 010,526,720 | ---- | M] () MD5=B3315DBDB28BD24D3AA4AC70566DCECB -- C:\Windows\Installer\5f6db.msi
[2015.05.08 ...
ok I studied them
you can delete 5f6db.msi, the package is corrupted , It won't never work anymore.
QuickDiag gave me the same message than it gave to you at the same moment , on the same file.
I tried to install it and Windows returned me an error message
all the msi files are signed and this not.
Regards
hello ok :)
would you like to send me these files :
[2015.09.22 17.16.32 | 000,774,144 | ---- | M] () MD5=9F39DC9027B92456016455A32B68478D -- C:\Windows\Installer\3ef7a91.msi
[2016.06.02 06.48.41 | 002,772,992 | R--- | M] () MD5=557170C4FCC0754B372A5FC174735242 -- C:\Windows\Installer\427ad05.msp
[2016.05.19 05.30.11 | 001,429,504 | R--- | M] () MD5=C233BD1DB45AF8BACD0F3C0D8A646740 -- C:\Wi...
Hello!
Well, like I mentioned before, I was not sure if this was the right file, so in that case, the right file would be this: 5f6db.msi in stead.
However, this file does not have any signers. I tried to run it, but it would not run either, so it appears to be broken.
He...
hello
I'm surprised cause I only control and read msi files with quickdiag, not .msp files.....
$aList = _FileListToArray(@WindowsDir & "\Installer", "*.msi", 1)
You're the only having this problem, I don't have anymore returns from others users about that ....
Regards
Hello!
The problem still persists; now it is on line 7975.
I am sorry I forgot to include the MD5 for the above mentioned file, so I thought I should run a script with OldTimer's List-It (OTL) in order to provide you with MD5 for all the *.mp* files in the said folder, here it is:
========== Custom Scans ==========
< C:\Windows\Installer\*.ms* /md5 >
[2015.03.17 10.48.34 | 002,800,128 |...
Hello,
Do you have a screenshot of the following ?
Have tried cleaning files indiviudally and it got halfway through a taskbar saying cleaning web entries or something alike then not responding popped up on the application window again.
Does the cleaning ends well if you uncheck every checkboxes from the File/Folders tab ?
Do you have any security software running ?
Thanks for your help,
Get Malwarebytes for powerful protection against adware and threats.
Get Malwarebytes Now