Plugin Updater keeps faililng

[mirandam]

Starting about 2 years ago, my miranda-ng updates always fails with "Unpack operation failed with error code=32, update terminated"

In short:

1. After starting Miranda, I get a "Updates Found!" prompt and click Update
2. After all downloads are successful, I get "Unpack operation failed with error code=32, update terminated"
3. If I close Miranda, download the latest release manually and replace the files in my Miranda folder, everything works (but it is tedious manual work)
4. I did raise this https://github.com/miranda-ng/miranda-ng/issues/4418 1 year ago but was brushed off as a file locking problem despite trying to engage in logic
5. If it was indeed some non-Miranda process locking some files, why does my step 3 succeed?
6. Can someone help me find the cause of this?

Thank you.

[ghazan]

>net helpmsg 32
The process cannot access the file because it is being used by another process.

I strongly suspect that your antivirus is too curious, another popular reason of this error is Windows Index Service.
Anyway, you can open System Informer / Process Hacker / whatever, enter the name of your archive and receive the id of a process which blocks it

[mirandam]

What you describe is a false dichotomy: The only possiblity to get a error 32 is because of A or B and nothing else.

If antivirus/Windows Index Service or whatever else lock the file, how come they so kindly let me replace Miranda files without errors (after I close Miranda)?

Have you considered Miranda might be the problem?

[mirandam]

Anyone?

[ghazan]

Have you considered Miranda might be the problem?

Miranda cannot lock a file for itself. It's so simple to detect who's locking a file, why wouldn't you try to do that?

[mirandam]

Ok, let's roll with that.

1. The red box has very little information and prevents me from clicking or checking on the greenbox
2. After I click the red box away, every file in the green box is "Succceeded."
3. Please enlighten me what process/file I should look or check for with System Informer.

[mirandam]

1. There are 29 entries for Miranda32.exe, including 1 by SystemInformer.
2. I closed SystemInformer and try to update
3. Still same error

[ghazan]

1. The red box has very little information and prevents me from clicking or checking on the greenbox

eh... why do you think that it's Miranda32.exe who caused that error?
you better create a network log with core + Plugin Updater, maybe there is more information?

[mirandam]

Why do I think it is Miranda32?

1. Because Miranda32 cannot update itself and complain about locking
2. If don't look at Miranda32.exe, then look at which file? That's why I did not want to use SystemInformer, but you said it is simple, now, it doesn't seem that simple anymore
3. If locking is indeed the problem, then how come I can manually replace the file once I close Miranda?
4. Yet, with so much info lacking and missing, you immediately conclude that it is an simple problem and cannot be Miranda
5. Now it has changed from file locking to network log problem...

When 1 to 5 all add together, the most likely problem is Miranda, whether it is a wrong reporting or self file locking because #3 is the elephant in the room which you don't have an explanation for the past 2 years

Perhaps I should also ask, why are you so sure it is not a bug in Miranda? For many years, Miranda was able to self update without problem, until around 2 years ago.

[ghazan]

1. Because Miranda32 cannot update itself and complain about locking

it has nothing to do with Miranda itself, Plugin Updater just downloads a bunch of zip files and tries to unpack them into the temporary folder

2. If don't look at Miranda32.exe, then look at which file? That's why I did not want to use SystemInformer, but you said it is simple, now, it doesn't seem that simple anymore

The file name shall be written into the network log, like "cannot open blablabla.zip, error 32"

3. If locking is indeed the problem, then how come I can manually replace the file once I close Miranda?

As I said, it doesn't rely to Miranda itself. Also, this problem might be caused by the absence of pu_stub.exe, if Miranda's files are located inside %ProgramFiles%

4. Yet, with so much info lacking and missing, you immediately conclude that it is an simple problem and cannot be Miranda

I know pretty well what Plugin Updater does.

5. Now it has changed from file locking to network log problem...

you cannot read it? what's the problem with the network log?

[mirandam]

1. Where do I find the network log file?
2. and which temporary folder is Plugin Updater trying to unpack to?
3. I run Miranda32 from my own folder, i.e. portable mode, no %ProgramFiles% involved.. for what it is worth, treat it as running from D:\miranda32\

[dartraiden]

Netlog

PU uses %miranda path%\Plugin Updates\Temp

[mirandam]

Same error, no sign of logs anywhere

Code: [Select]

D:\miranda>dir/s
 Volume in drive E is xxx
 Volume Serial Number is 9337-7D0E

 Directory of D:\miranda

05/12/2025  08:19 AM    <DIR>          .
05/12/2025  08:19 AM    <DIR>          ..
05/12/2025  08:19 AM    <DIR>          Backups
05/12/2025  08:19 AM    <DIR>          Temp
               0 File(s)              0 bytes

 Directory of D:\miranda\Backups

05/12/2025  08:19 AM    <DIR>          .
05/12/2025  08:19 AM    <DIR>          ..
               0 File(s)              0 bytes

 Directory of D:\miranda\Temp

05/12/2025  08:19 AM    <DIR>          .
05/12/2025  08:19 AM    <DIR>          ..
05/12/2025  08:19 AM           231,628 clist_modern.zip
05/12/2025  08:19 AM            23,093 crashdumper.zip
05/12/2025  08:19 AM            13,819 dbchecker.zip
05/12/2025  08:19 AM           113,783 dbx_mdbx.zip
05/12/2025  08:19 AM            18,135 dbx_mmap.zip
05/12/2025  08:19 AM            19,411 dbx_sqlite.zip
05/12/2025  08:19 AM            24,828 db_autobackups.zip
05/12/2025  08:19 AM            14,448 dummy.zip
05/12/2025  08:19 AM            33,189 facebook.zip
05/12/2025  08:19 AM           127,477 gg.zip
05/12/2025  08:19 AM            39,247 import.zip
05/12/2025  08:19 AM           103,733 irc.zip
05/12/2025  08:19 AM           710,518 jabber.zip
05/12/2025  08:19 AM            15,152 neweventnotify.zip
05/12/2025  08:19 AM            31,690 ping.zip
05/12/2025  08:19 AM            43,297 pluginupdater.zip
05/12/2025  08:19 AM            15,798 quickmessages.zip
05/12/2025  08:19 AM             8,503 quickreplies.zip
05/12/2025  08:19 AM             9,827 removepersonalsettings.zip
05/12/2025  08:19 AM            74,566 scriver.zip
05/12/2025  08:19 AM            44,059 statusmanager.zip
05/12/2025  08:19 AM           242,210 tabsrmm.zip
05/12/2025  08:19 AM            20,650 toptoolbar.zip
05/12/2025  08:19 AM            23,784 voiceservice.zip
              24 File(s)      2,002,845 bytes

     Total Files Listed:
              24 File(s)      2,002,845 bytes
               8 Dir(s)  510,978,949,120 bytes free

D:\miranda>

[ghazan]

is disk D: writeable?
anyway, it seems that the simplest way to detect the problem is Process Monitor. Run it, add Miranda32.exe as a filter, reproduce the problem and then find error 32 in ProcMon's log

[mirandam]

so much for antivirus