Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Huge number of opera ".dll" files in windows/temp folder

  • Hi,

    I'm okay with temporary files for any soft that need to be updated or is updating.

    But in my case, files are created each time Opera starts, even if it is up to date.

    And sometime, one file is created, but other times it can create several in few seconds... And all the files are strictly the same. This point doesn't seem to be normal at me (I have computer skills, that's why I am surprised by this operation).

  • @dede6 I must agree. I have 6 various browsers on this Win10Pro-1709 system, and Opera is the only one that continually accumulates large numbers of dll files in the temp folder - and leaves them apparently 'forever'. The other browsers never do this, but for some reason, Opera can't seem to get Windows to flush after use.

  • @dede6 Did you try a clean installation? I've checked here and Opera seems to only create those files when doing auto-update.

  • @leocg On my system, an Opera_installer_yymmddtttt####.dll file is created and saved in the temp folder each time Opera is restarted (where yymmdd are the usual digits for year, month, day and tttt are UT time digits and #### are 'unknown' digits that change for each file).

    Since I often use multiple browsers via opening and closing each rather frequently (on occasion, multiple times each day), the number of Opera files in the temp folder can increase dramatically over time. Each file is 2.1 mB, so it does eventually add up unless they're cleaned out periodically.

    Closing/restarting Opera immediately causes another file to be created - that is, there seems to be no time delay or limiting... a new, additional file appears every single time the browser is started.

  • @blackbird71 Here I see a CProgram FilesOpera developer53.0.2885.0opera_autoupdate.download.lock file, that seems to be 0 bytes, being created in the temp folder when Opera starts. No dll files.

  • @dede6 said in Huge number of opera ".dll" files in windows/temp folder:

    But in my case, files are created each time Opera starts, even if it is up to date.

    I can't reproduce that.

    And sometime, one file is created, but other times it can create several in few seconds.

    The installer sometimes creates 4 - 6 of them for example. Looking at the log files in the "opera installer" folder in the temp folder, I see that sometimes one of the logs tries something and fails, which may be while it tries again. But, the other logs show that things were fine, so I'm not sure.

    What's the path to Opera's launcher.exe? Is it just "C:\Program Files\Opera\launcher.exe"?

  • @blackbird71 said in Huge number of opera ".dll" files in windows/temp folder:

    On my system, an Opera_installer_yymmddtttt####.dll file is created and saved in the temp folder each time Opera is restarted

    Can you delete the Opera program files directory and install again (with the offline installer just for good measure) and see if it still does it?

  • @burnout426 said in Huge number of opera ".dll" files in windows/temp folder:

    with the offline installer

    with the offline installer ya get lottsa o files in this Temp director too..

    • Users\user's name\AppData\Local\Temp\Opera Installer -
      this is a sum of files but lottsa more o log files, to many to count lol

    the exe files work and will re-install opera if ya click 'em..

    0_1520998817575_50147722-bb06-41b1-9e22-52c32e23b1f6-image.png

  • @burnout426 said in Huge number of opera ".dll" files in windows/temp folder:

    ...
    Can you delete the Opera program files directory and install again (with the offline installer just for good measure) and see if it still does it?

    As in 'delete the \program files\opera\51.0.2830.55 folder' and not by "uninstalling" Opera? I'd prefer not to screw things up by doing it wrong.

    By the way, due to a family medical crisis, I may be slow to respond here over the next few days.

  • @blackbird71 said in Huge number of opera ".dll" files in windows/temp folder:

    As in 'delete the \program files\opera\51.0.2830.55 folder' and not by "uninstalling" Opera?

    The whole "opera" folder. You don't need to run an uninstall, but you can if you want to make sure the program and features entry for Opera is cleared and recreated when you reinstall.

    I may be slow to respond here over the next few days.

    Understood. No problem.

  • @burnout426 Thanks for the suggestion, but it seems not to have altered the situation. I uninstalled Opera and purged the \windows\temp folder of all the various opera-related files, reinstalled Opera (as admin) using the offline installer, started/closed Opera a few times, and the problem immediately reappeared. That is, a copy of the earlier-described files are separately written for each Opera start occurrance. The only difference noted is that the file size is 1.814 mB instead of the prior 2.0+ mB. In looking into these files themselves with Wordpad, the contents below the half-way point include a great deal of plain-text in various languages that each appear to replicate the various text of Opera's installer-panel options, labels, possible response messages, etc. That seems to correlate with the files' name structure of Opera_installer_yymmddtttt####.dll (with the symbology interpretations I noted earler). For me, it's not that big of a problem to occasionally go in and manually scrub the temp folder of these files as I've been doing, but I can't speak for other users like the OP, @dede6.

  • @blackbird71 said in Huge number of opera ".dll" files in windows/temp folder:

    In looking into these files themselves with Wordpad, the contents below the half-way point include a great deal of plain-text in various languages that each appear to replicate the various text of Opera's installer-panel options,

    Hmm that weird that Opera would generate them on startup and not just when installing/updating. What's your OS locale? Maybe if it's not en-US, Opera generates them automatically on startup for some reason.

    For me, it's not that big of a problem to occasionally go in and manually scrub the temp folder of these files

    Same here. Although, I think Opera could do some cleanup here just to be neat.

  • @burnout426 said in Huge number of opera ".dll" files in windows/temp folder:

    ... Hmm that weird that Opera would generate them on startup and not just when installing/updating. What's your OS locale? Maybe if it's not en-US, Opera generates them automatically on startup for some reason. ...

    I'm in the US midwest. About all I know is that this has been going on for some time with regard to both Opera and Windows versions on this 9-month-old desktop system, under both the original 1703 and 1709-upgrade Windows 10 Pro versions of OS. The older-dated files have been deleted during a couple of clean-up efforts, so I don't know the exact starting point in time... I do know that the last round of cleanup involved file dates starting around late January. Opera is set to (and does) allow auto-updating and those have been successfully occurring. Otherwise, Opera and my other browsers all run fine and uneventfully. Perhaps it's just another of the many mysteries involving programs running under Windows 10... 😉

  • @leocg said in Huge number of opera ".dll" files in windows/temp folder:

    @dede6 Those files aren't unuseful, they are created when Opera is installed or updated and should be removed (by Windows?) after that but it isn't.
    Every time you install or update a software, it will write temporary files to the %temp% folder.

    First, no third-party application should write into windows\temp folder - this is used by some windows programs (win defender, click-to-run telemetry) and/or in cases, when some non-interactive account (without folder in Users) requires temporary space. windows\temp is not %temp%. Looking at file security it seems that these files are created by system account - would it not our beloved Opera, I would ban such behavior.

    Second, I see these dll files created multiple times each day (after starting opera), those are identical byte-by-byte (up to next real update), only creation time (and file name, which are correlated) differs by few hundreds milliseconds. This is clearly an error from opera updater side. Dev stream here.

    Waiting for fixes. Patiently.

  • @blackbird71 said in Huge number of opera ".dll" files in windows/temp folder:

    Perhaps it's just another of the many mysteries involving programs running under Windows 10... 😉

    Could happen with programs, written in 1995 or so. Should never happen with current software. Windows 10 is not to blame, at least not in this regard.

  • I've just ran Opera installer to test and could see an 'opera installer' folder and a couple of dll files being created on %temp%.
    I removed them, started Opera and no such files were created, just two lock files related to metrics.
    Running the auto-update will create the 'opera installer' folder if there is an update but no dll files.

  • @leocg
    In %temp% are only few Opera .lock files. In windows\temp are dlls.
    It could be scheduled opera autoupdate task, which seems to run under SYSTEM account. I start and shut down my pc daily - no sleeps here, on desktop system.
    Well, looks like it is so - dll files are created at system startup and at 20:31 - which are exactly scheduled triggers for running it. D**n, I hate any automatic updates. Apparently I have to disable/remove it.

  • @donq OK, I've found those dlls created by the installer in windows\temp, removed them, started Opera and no new files were created in that folder.

  • FWIW, if I rename Opera's installer.exe file (eg: xxxinstaller.exe) in the Opera program folder, starting up Opera no longer causes the Opera_installer_yymmddtttt####.dll files to be written to the \windows\temp folder. Renaming it back to installer.exe causes the file writing at each Opera startup to resume. Something seems to be occurring at Opera startup that either invokes something in, or copies something from, the installer.exe file and creates a new dll in the temp folder... renaming the installer.exe file seems to block that process, whatever it is.

  • Yeah, I can confirm now on the dll files. I was looking at %temp% instead of %windir%\temp. Sorry. Thanks @blackbird71 .