missing SDL2.dll after installation #49508

New Issue

Michael Calmbach · 2016-09-30T20:49:47+02:00

Michael Calmbach commented

2016-09-30 20:49:47 +02:00

System Information
Windows 10 64 32 GB Ram

Blender Version
Broken:: Blender 2.78 Date 2016-09-26 12:42
Worked: (optional)

Blender dosn't start it misses SDL2.dll after installation

Added from nighly build the SDL2.dll to the Blender Path then it starts

Michael

**System Information** Windows 10 64 32 GB Ram **Blender Version** Broken:: Blender 2.78 Date 2016-09-26 12:42 Worked: (optional) Blender dosn't start it misses SDL2.dll after installation Added from nighly build the SDL2.dll to the Blender Path then it starts Michael

Michael Calmbach self-assigned this 2016-09-30 20:49:47 +02:00

Michael Calmbach commented

2016-09-30 20:49:47 +02:00

Changed status to: 'Open'

Michael Calmbach commented

2016-09-30 20:49:47 +02:00

Added subscriber: @MichaelCalmbach

blender-admin commented

2016-09-30 20:49:47 +02:00

#49569 was marked as duplicate of this issue

blender-admin commented

2016-09-30 20:49:47 +02:00

#49549 was marked as duplicate of this issue

blender-admin commented

2016-09-30 20:49:47 +02:00

#49554 was marked as duplicate of this issue

blender-admin commented

2016-09-30 20:49:47 +02:00

#49525 was marked as duplicate of this issue

Tom commented

2016-09-30 23:35:15 +02:00

Added subscriber: @Tommy-8

Tom commented

2016-09-30 23:35:15 +02:00

I have same issue when installing on two separate Windows 10 machines. I got it working on both by re-installing package and choosing "repair installation", then all seems fine.

Tom

I have same issue when installing on two separate Windows 10 machines. I got it working on both by re-installing package and choosing "repair installation", then all seems fine. Tom

DelDadam commented

2016-10-01 00:24:51 +02:00

Added subscribers: @tom-37, @PeterToth

DelDadam commented

2016-10-01 00:24:51 +02:00

Same here as at Tom (Tommy), but on Win. 8.1 64-bit. Used 'Repair' option of the MSI setup, and it has fixed the issue.

DelD.

Same here as at Tom (Tommy), but on Win. 8.1 64-bit. Used 'Repair' option of the MSI setup, and it has fixed the issue. DelD.

Michael Calmbach was unassigned by Bastien Montagne

2016-10-01 08:42:48 +02:00

Brecht Van Lommel commented

2016-10-01 22:58:02 +02:00

Added subscriber: @rickyblender

Kai Mach commented

2016-10-01 22:58:08 +02:00

Added subscriber: @kai_mach

Kai Mach commented

2016-10-01 22:58:08 +02:00

The repair option did the trick for me as well. I'm on Win 7 x64.

Charlie Park commented

2016-10-02 00:38:02 +02:00

Added subscriber: @ChurowPark

Charlie Park commented

2016-10-02 00:38:02 +02:00

Same here. Fixed by "Repair"

Ricky J commented

2016-10-02 14:26:08 +02:00

tried latest built and still missing SDL2.dll

I re install it and use the repair function
and now seems to work
it did create in app folder on win 64 a new config folder

but it did not use the old config from 2.77
so I had to copy old config folder to the 2.78 folder manually

thanks
happy bl

tried latest built and still missing SDL2.dll I re install it and use the repair function and now seems to work it did create in app folder on win 64 a new config folder but it did not use the old config from 2.77 so I had to copy old config folder to the 2.78 folder manually thanks happy bl

JT Nelson commented

2016-10-02 18:20:38 +02:00

Added subscriber: @jta

JT Nelson commented

2016-10-02 18:20:38 +02:00

A couple pokes in the dark here. Maybe a virus scanner is blocking the expanding of that dll from a false positive or just holding it up during scanning might be causing the installer to not copy the file. I've had virus scanners hold things up before and cause similar issues in general.

Also this dll missing issue seems to be a common for downloaded games. So maybe it's an installer issue confusing the 32/64 bit versions? The installer usually does an ok job with the ver utility properly identifying dll versions so maybe there's a bug there or in the install script? Then somehow the installer fixes it on repair I see posted here.

Again just poking in the dark and helping out by harassing some of the usual suspects...

A couple pokes in the dark here. Maybe a virus scanner is blocking the expanding of that dll from a false positive or just holding it up during scanning might be causing the installer to not copy the file. I've had virus scanners hold things up before and cause similar issues in general. Also this dll missing issue seems to be a common for downloaded games. So maybe it's an installer issue confusing the 32/64 bit versions? The installer usually does an ok job with the ver utility properly identifying dll versions so maybe there's a bug there or in the install script? Then somehow the installer fixes it on repair I see posted here. Again just poking in the dark and helping out by harassing some of the usual suspects...

Brecht Van Lommel commented

2016-10-02 19:07:53 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2016-10-02 19:07:53 +02:00

If anyone can still reproduce this, attaching the MIS installer log to this report might provide a clue. You can generate that by running the installer like this from a command prompt (windows key + R, type cmd), adapt the path as needed:

msiexec /i C:\Users\%USERNAME%\Downloads\blender-2.78-windows64.msi /L*v blender-2.78-install-log.txt

Further useful information could be:

Is the user account an administrator or not?
After failed installation, can SDL2.dll be found somewhere on your system (perhaps in the wrong folder), or is it not there at all?
If you open the Windows Event Viewer, is there anything relevant in the logs?
Which if any virus scanner do you use? Is there anything about this in the virus scanner logs?

If anyone can still reproduce this, attaching the MIS installer log to this report might provide a clue. You can generate that by running the installer like this from a command prompt (windows key + R, type `cmd`), adapt the path as needed: ``` msiexec /i C:\Users\%USERNAME%\Downloads\blender-2.78-windows64.msi /L*v blender-2.78-install-log.txt ``` Further useful information could be: * Is the user account an administrator or not? * After failed installation, can SDL2.dll be found somewhere on your system (perhaps in the wrong folder), or is it not there at all? * If you open the Windows Event Viewer, is there anything relevant in the logs? * Which if any virus scanner do you use? Is there anything about this in the virus scanner logs?

claas eicke commented

2016-10-02 19:19:58 +02:00

Added subscriber: @ClaasKuhnen

claas eicke commented

2016-10-02 19:19:58 +02:00

@brecht

MacPro 2008
Win10
No extra Virus Scanner
Default Win Defender is running

I cannot find the SDL2.dll on the HD anywhere.

When entering your command I get this:

@brecht MacPro 2008 Win10 No extra Virus Scanner Default Win Defender is running I cannot find the SDL2.dll on the HD anywhere. When entering your command I get this: ![Capture.PNG](https://archive.blender.org/developer/F372792/Capture.PNG)

Brecht Van Lommel commented

2016-10-02 19:29:33 +02:00

Thanks for testing. To generate the log, you would first uninstall Blender. Then you would run this command to install it again, and the log file will be at c:\Users\info\blender-2.78-install-log.txt after installation is completed.

Ideally (for us) the SDL2.dll error would happen also after this second installation, though even if Blender then runs without the error the log may have useful information.

Thanks for testing. To generate the log, you would first uninstall Blender. Then you would run this command to install it again, and the log file will be at c:\Users\info\blender-2.78-install-log.txt after installation is completed. Ideally (for us) the SDL2.dll error would happen also after this second installation, though even if Blender then runs without the error the log may have useful information.

claas eicke commented

2016-10-02 19:36:42 +02:00

@brecht

Blender runs now
The SDL2.dll is in the folder - I did not check before if it was visually there
blender-2.78-install-log.txt

@brecht Blender runs now The SDL2.dll is in the folder - I did not check before if it was visually there [blender-2.78-install-log.txt](https://archive.blender.org/developer/F372803/blender-2.78-install-log.txt) ![Capture.PNG](https://archive.blender.org/developer/F372801/Capture.PNG)

mathieu menuet commented

2016-10-02 19:58:04 +02:00

Added subscriber: @bliblubli

mathieu menuet commented

2016-10-02 19:58:04 +02:00

For me it only fails when installing the first time over 2.77a. Repairing or desinstalling then reinstalling resolves the problem.

DelDadam commented

2016-10-02 20:02:28 +02:00

Funny. Can't reproduce the issue anymore.

1st attempt:

Blender uninstalled.
AV switched off (using COMODO).
Re-installed using Brecht's command.
After installation the SDL2.dll was present on the install path, log file created (no issues found in it, SDL2.dll was recognized as missing, so it was copied), Blender started w/o any issue.

2nd attempt:

Uninstalled prev. Bl. copy.
I've kept AV active (as it was when I've 1st time installed Bl. 2 days ago).
MSI installer started same way as 2 days ago (by right clicking on it in the explorer.)
After installation the SDL2.dll was present on the install path again, Blender works fine.

The only difference between now and 2 days ago: my AV was updated yesterday to a new version and virus db.

No idea what's going on.

Cheers,

DelD.

Funny. Can't reproduce the issue anymore. `1st attempt:` - Blender uninstalled. - AV switched off (using COMODO). - Re-installed using Brecht's command. - After installation the SDL2.dll was present on the install path, log file created (no issues found in it, SDL2.dll was recognized as missing, so it was copied), Blender started w/o any issue. `2nd attempt:` - Uninstalled prev. Bl. copy. - I've kept AV active (as it was when I've 1st time installed Bl. 2 days ago). - MSI installer started same way as 2 days ago (by right clicking on it in the explorer.) - After installation the SDL2.dll was present on the install path again, Blender works fine. The only difference between now and 2 days ago: my AV was updated yesterday to a new version and virus db. No idea what's going on. Cheers, DelD.

DelDadam commented

2016-10-02 20:04:52 +02:00

Ahha. I've left out the scenario mentioned by bliblu bli - installing over 2.77a... That's another difference to the state of my PC 2 days ago.

Ricky J commented

2016-10-02 21:46:50 +02:00

I found 2 errors fir bl

1 -

Application 'H:\Program Files\Blender Foundation\Blender\blender.exe' (pid 2844) cannot be restarted - Application SID does not match Conductor SID..

2 -

if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 26b8
Start Time: 01d21b6bd4105a33
Termination Time: 17
Application Path: H:\Program Files\Blender Foundation\Blender\blender.exe
Report Id: 798f9ed1-875f-11e6-b5a8-a4db302dab58
Faulting package full name:
Faulting package-relative application ID:

also nee to follow this

blender error / bug
You could also look up the Event Viewer application, then click Administrative Events, click the Source header to sort by source type, look for Application Error sources, then look for an error dealing with blender.exe. (check the date to make sure it's the error you just had, not something from a year ago)

thanks for reminding this little log on win

thanks
happy bl

I found 2 errors fir bl 1 - Application 'H:\Program Files\Blender Foundation\Blender\blender.exe' (pid 2844) cannot be restarted - Application SID does not match Conductor SID.. 2 - if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 26b8 Start Time: 01d21b6bd4105a33 Termination Time: 17 Application Path: H:\Program Files\Blender Foundation\Blender\blender.exe Report Id: 798f9ed1-875f-11e6-b5a8-a4db302dab58 Faulting package full name: Faulting package-relative application ID: also nee to follow this blender error / bug You could also look up the Event Viewer application, then click Administrative Events, click the Source header to sort by source type, look for Application Error sources, then look for an error dealing with blender.exe. (check the date to make sure it's the error you just had, not something from a year ago) thanks for reminding this little log on win thanks happy bl

Brecht Van Lommel commented

2016-10-02 21:50:09 +02:00

I managed to repro the problem now on Windows 10, by uninstalling all Blender versions, installing Blender 2.77a, 64bit and then installing Blender 2.78 64bit over that.

Heres the log: blender-2.78-install-log.txt. We can see SDL2.dll getting remove but not re-added, unlike the other dlls. At the install validation stage, SDL2.dll is the only file which has Action: Null.

There is this message, where DA74128A-0D77-5E97-B3A1-3C0AF6EE9F9B corresponds to SDL2.dll.

MSI (c) (04:5C) [21:22:33:131]: Disallowing installation of component: {DA74128A-0D77-5E97-B3A1-3C0AF6EE9F9B}
since the same component with higher versioned keyfile exists

I don't understand yet how these version numbers are determined. This seems relevant:
https://blogs.msdn.microsoft.com/astebner/2015/11/16/why-windows-installer-removes-files-during-a-major-upgrade-if-they-go-backwards-in-version-numbers/

I managed to repro the problem now on Windows 10, by uninstalling all Blender versions, installing Blender 2.77a, 64bit and then installing Blender 2.78 64bit over that. Heres the log: [blender-2.78-install-log.txt](https://archive.blender.org/developer/F372853/blender-2.78-install-log.txt). We can see SDL2.dll getting remove but not re-added, unlike the other dlls. At the install validation stage, SDL2.dll is the only file which has `Action: Null`. There is this message, where `DA74128A-0D77-5E97-B3A1-3C0AF6EE9F9B` corresponds to `SDL2.dll`. ``` MSI (c) (04:5C) [21:22:33:131]: Disallowing installation of component: {DA74128A-0D77-5E97-B3A1-3C0AF6EE9F9B} since the same component with higher versioned keyfile exists ``` I don't understand yet how these version numbers are determined. This seems relevant: https://blogs.msdn.microsoft.com/astebner/2015/11/16/why-windows-installer-removes-files-during-a-major-upgrade-if-they-go-backwards-in-version-numbers/

Brecht Van Lommel commented

2016-10-02 21:51:13 +02:00

Added subscriber: @LazyDodo

Brecht Van Lommel commented

2016-10-02 23:07:28 +02:00

So the file version is embedded in the SDL2.dll itself. The one included in 2.77a has version 2.0.4.0, the one included in 2.78 has 2.0.3.0. This can be verified by simply right clicking on the file and looking at Properties > Details.

@LazyDodo, I guess you might have more insight in how the SDL2.dll could have ended up with a lower version? The solution may be to rebuild SDL, ensuring it's using version 2.0.4.0 or higher?

This MSI behavior makes no sense to me, but from reading various online sources it seems that this is just how it works. To prevent this in the future I guess we would always have to test installing over an old version, though it would be nice if we had a more automatic way of catching this.

So the file version is embedded in the SDL2.dll itself. The one included in 2.77a has version 2.0.4.0, the one included in 2.78 has 2.0.3.0. This can be verified by simply right clicking on the file and looking at Properties > Details. @LazyDodo, I guess you might have more insight in how the SDL2.dll could have ended up with a lower version? The solution may be to rebuild SDL, ensuring it's using version 2.0.4.0 or higher? This MSI behavior makes no sense to me, but from reading various online sources it seems that this is just how it works. To prevent this in the future I guess we would always have to test installing over an old version, though it would be nice if we had a more automatic way of catching this.

Ray molenkamp commented

2016-10-03 00:10:13 +02:00

Added subscriber: @MartijnBerger

Ray molenkamp commented

2016-10-03 00:10:13 +02:00

According to svn log, the last update to SDL in svn was in 2014 when it got bumped to 2.0.3.0, The only way 2.77a had 2.0.4.0 is if @MartijnBerger build the previous installer with a tainted svn repo.

Seems silly to upgrade a library just to get around a wonky installer issue, but say the word and i'll update svn to 2.0.4.0

According to svn log, the last update to SDL in svn was in 2014 when it got bumped to 2.0.3.0, The only way 2.77a had 2.0.4.0 is if @MartijnBerger build the previous installer with a tainted svn repo. Seems silly to upgrade a library just to get around a wonky installer issue, but say the word and i'll update svn to 2.0.4.0

Brecht Van Lommel commented

2016-10-03 00:27:12 +02:00

I suggest to just upgrade, I don't have a better solution.

Ray molenkamp commented

2016-10-03 01:17:14 +02:00

Done! rBL61732 and rBL61733

Brecht Van Lommel commented

2016-10-03 10:47:30 +02:00

Ok, I think we need a new installer with just this fix? Or we could wait for 2.78a, but personally would rather see this fixed as soon as possible.

Dalai Felinto commented

2016-10-03 16:52:25 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2016-10-03 16:52:25 +02:00

+1 for a new installer . I'm glad you figured this out @brecht !

Ray molenkamp commented

2016-10-03 16:57:56 +02:00

Issuing a new installer with the same version number, while a solution for this problem, will open up another can of worms (see #49200) It's probably better that we fix this in 2.78a