Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Installer leaves a mess

vefatica

vefatica

May
13,748
209
When I read "new installer version" I was excited ... maybe it'll stop leaving a mess in %TEMP ... not the case!
Code: 
2014-12-22  22:26  480  {880FBB26-9B6A-4AA8-AB95-4C6A43ED3BFE}.bat
2014-12-22  22:28  735,110  MSIA66D.LOG
2014-12-22  22:28  441  EXE69A3.tmp.bat
2014-12-22  22:28  441  EXE69C3.tmp.bat
2014-12-22  22:28  <DIR>  777db8356beda08e2acf1fdf26cc6b7f
 
TEA-Time said:
Might those be marked for deletion on next reboot? (yeah, right. heh)

Something like SysInternals' PendMoves would tell you.

http://technet.microsoft.com/en-us/sysinternals/bb897556
Click to expand...
I doubt it. The registry key for that is empty (and hasn't been used in years). And PendMoves finds nothing.

Each of the three bat files have an instruction to delete itself. One of them has an instruction to remove the (empty) directory. Note of that gets done.
 
TEA-Time said:
Just curious what makes you think that? Windows updates for one use the heck out of that feature because files that are in use need replaced.
Click to expand...
Code: 
v:\> keytimes hklm "filerenameoper"
2009-07-14  00:37:09  HKLM\SYSTEM\ControlSet001\Control\Session Manager\FileRenameOperations
2009-07-14  00:37:09  HKLM\SYSTEM\ControlSet002\Control\Session Manager\FileRenameOperations
2009-07-14  00:37:09  HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\FileRenameOperations
 
Oh.. that's not the right place. I don't know what that is, but PendingFileRenameOperations is a value, rather than a key name, under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager. Since PendMoves reports nothing, I believe that value might not even be there.
 
I had also done this, with no success.
Code: 
v:\> regfind PendingFileRenameOperations
That searches keys, values, and data.
 
And the last time the "Session Manager" key was written to was
Code: 
2014-12-22  21:10:27  HKLM\SYSTEM\CurrentControlSet\Control\Session Manager
an hour before my upgrading TCMD.
 
Like I suspected, that PendingFileRenameOperations value only exists when there's something to do, and then it's deleted after it's processed.
 
TEA-Time said:
Like I suspected, that PendingFileRenameOperations value only exists when there's something to do, and then it's deleted after it's processed.
Click to expand...
Yeah, but whenever it's created or deleted, the time stamp on the "Session Manager" key would be updated. The content of that key hasn't changed since before my TCMD update.
 
That probably means that all the files that needed replaced could be done without having to restart Windows. You didn't have to reboot, right? Windows only processes that value when it's booting up, before anything has a chance to start and lock a file.
 
TEA-Time said:
That probably means that all the files that needed replaced could be done without having to restart Windows. You didn't have to reboot, right? Windows only processes that value when it's booting up, before anything has a chance to start and lock a file.
Click to expand...
Right. I don't think TCMD updates use that mechanism anyway. But updates always leave that mess in %TEMP.
 
You must log in or register to reply here.
Back
Top