Terminating program update thread takes longer than before

[dbminter]

I swapped my 2 year old Pioneer Blu-Ray burner for a newer version of the same model.  After installing the new drive, ImgBurn does something it didn't before.  On closing down of ImgBurn, it says Terminating Program Update Thread... and takes about 30 to 60 seconds before ImgBurn closes.  Earlier in the day with the old Pioneer, ImgBurn would close down immediately.

 

 

Is this something I should be worried about regarding the new Pioneer drive?  That maybe it arrived defective?

 

 

Here's the log, not that it will be helpful. 

 

 

I 18:14:41 Project Successfully Loaded!
I 18:14:41 ImgBurn Version 2.5.8.0 started!
I 18:14:41 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 18:14:41 Total Physical Memory: 12,532,940 KiB  -  Available: 8,226,820 KiB
I 18:14:41 Initialising SPTI...
I 18:14:41 Searching for SCSI / ATAPI devices...
I 18:14:41 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI)
I 18:14:41 -> Drive 2 - Info: PIONEER BD-RW   BDR-209M 1.33-ID60 (S:) (SATA)
I 18:14:41 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI)
I 18:14:41 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI)
I 18:14:41 -> Drive 5 - Info: PIONEER BD-RW   BDR-209M 1.33-ID60 (K:) (SATA)
I 18:14:41 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs!

I 18:14:55 Close Request Acknowledged
I 18:14:55 Closing Down...
I 18:15:44 Shutting down SPTI...
I 18:15:44 ImgBurn closed!

 

 

Thanks!

[dbminter]

Hm, it went away! 

 

 

Is the Program Update Thread just a check for new versions?  Probably not because isn't that done at the startup of ImgBurn?  If it is just a check for new versions, then the update server might have been unresponsive.

[LIGHTNING UK!]

Yes, it's just a check for program updates and yes, it's initiated at launch.

 

It won't be related to your drive swap, it'll just be due to a connectivity issue or firewall.

[dbminter]

Is it also initiated at program shut down?

[LIGHTNING UK!]

No.

 

It closes the threads down when it's closed though and that's why you're seeing that message.

 

Normally it would do the update check and terminate within a few seconds of opening the program, but yours got stuck for some reason.

[dbminter]

Yeah, it was temporary for some reason.  I tried everything I could think of that might help it.  Closing down Windows, powering off the system, letting it off for a minute, restarting the PC and Windows, tried ImgBurn again and it still was present.  Then, it just went away.  Go figure!