I have used Regshot 1.9.0 relating to the app TeamViewer Portable 8.0.16642 and in the report was noted in the section "Files added" the following content:
C:\Dokumente und Einstellungen\Andreas Piatek\Lokale Einstellungen\Temp\nsh3C.tmp\Registry.dll
Due to this report I must assume, that TeamViewer Portable 8.0.16642 leaves a folder with content (here: nsh3C.tmp\Registry.dll) in %LOCALAPPDATA%\Temp. After restarting my computer I found however, that this folder was gone. Accordingly are the results with Regshot 1.9.0 not completely sufficient.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Did you wait for the launcher to fully close?
Previously known as kAlug.
The app was completely closed, i.e. that means also the launcher. Please test it yourself.
Thats the dll of NSIS's Registry plugin. If it disappeared after rebook, maybe it was set to be deleted later by the OS?
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Of course that explains everything. Thanks
EDIT: But this does not change the fact that the report is somehow unclear, when I must consider those special circumstances.
With RegShot you always have to consider special circumstances.
RegShot does not promise to only show you changes made by one executable - it shows every change that occurs between the first and second shots - including related and unrelated entries from your firewall, antivirus, Windows itself, plus any other program that may be running at the time.
If you want only the registry changes from a single executable you use RegFromApp - but its downside is that it doesn't report file changes like RegShot does.
I have never expected, that Regshot 1.9.0 only shows the changes, which are caused by a single executable. But how I already have mentioned, in the report appears in the section "Files added" some entries. Accordingly I must assume, that this statement is true. If I then after restarting of my computer notice the opposite, then confirmed that my above statement that the report is not sufficient. I even believe that this is a bug in the program.
Of course may the entry, which I have mentioned in my original post, also be caused by other things like my firewall, antivirus, any other program and, and ...
With the following explanations I will, however, prove conclusively that this entry is caused exclusively by the program TeamViewer.
Often the path contains informations about the application (for example the name of the application). However such informations appear in the above path nowhere.
If for example an antivirus program would cause the above entry, then this entry would also be displayed in the reports, which I create with Regshot with respect to other portable applications. Accordingly I have created for 3 arbitrary apps (VLC PLayer, Audacity and PeaZip) with Regshot an appropriate report. And in none of these reports, a similar entry appeared as the above mentioned.
Due to the above explanations is surely uniquely proved, that the above mentioned entry is caused exclusively by the program TeamViewer.
The above research I have not done on my own computer. Instead I used the computer of a friend, on which the operating system Windows Vista Home Premium 64-Bit is installed. And here I was able to determine that the file Registry.dll even after a restart of the computer was still present.
I can clear this up. There is a bug in the current TeamViewer Portable launcher where it will leave the registry plugin behind. This will be rectified in the next TeamViewer release where they switch to my updated launcher based on PAL.
Sometimes, the impossible can become possible, if you're awesome!
that they finally update their launcher. It was getting a bit old.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate