Installer of 2.81 is detected by Windows Defender Smartscreen and weird installation #71784

New Issue

Emmanuel LORANT · 2019-11-22T16:34:04+01:00

Emmanuel LORANT commented

2019-11-22 16:34:04 +01:00

System Information
Operating system: Windows 10 x64 Pro
Graphics card: GTX 1060 6Gb

Blender Version
Broken: 2.81 release
Worked: (optional)

Short description of error

It's the first version where it happens. I donwloaded the blender-2.81-windows64.msi for Windows 10 x64 https://www.blender.org/download/, I executed it and Windows Defender Smartcreen warned me as it can be dangerous (it usually does this with the daily builds). I executed it anyway, let all by default as usual and instead
of overriding the previous version, it creates a new folder "Blender 2.81" in Programs/Blender Foundation and I have 2 Blender in Applications & Functionalities of Windows 10.

2 questions :

why is it detected by Windows Defender Smartscreen ?
is it a new way for the installation to work ?

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 10 x64 Pro Graphics card: GTX 1060 6Gb **Blender Version** Broken: 2.81 release Worked: (optional) **Short description of error** It's the first version where it happens. I donwloaded the blender-2.81-windows64.msi for Windows 10 x64 https://www.blender.org/download/, I executed it and Windows Defender Smartcreen warned me as it can be dangerous (it usually does this with the daily builds). I executed it anyway, let all by default as usual and instead of overriding the previous version, it creates a new folder "Blender 2.81" in Programs/Blender Foundation and I have 2 Blender in Applications & Functionalities of Windows 10. 2 questions : - why is it detected by Windows Defender Smartscreen ? - is it a new way for the installation to work ? **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).

Emmanuel LORANT commented

2019-11-22 16:34:04 +01:00

Added subscriber: @EmmanuelLORANT

blender-admin commented

2019-11-22 16:34:04 +01:00

#73407 was marked as duplicate of this issue

blender-admin commented

2019-11-22 16:34:04 +01:00

#72649 was marked as duplicate of this issue

Keith Gadberry commented

2019-11-22 19:18:20 +01:00

Added subscriber: @KeithGadberry

Anthony Edlin commented

2019-11-22 22:51:56 +01:00

Added subscriber: @AnthonyEdlin

Anthony Edlin commented

2019-11-22 22:51:56 +01:00

I think once there is data from a bunch of people accepting install past smartscreen warning it will eventually just allow it.

Not sure about installation directory but probably is intended because having multiple versions of blender is pretty common use case.

I think once there is data from a bunch of people accepting install past smartscreen warning it will eventually just allow it. Not sure about installation directory but probably is intended because having multiple versions of blender is pretty common use case.

Ajlan Altug commented

2019-11-22 23:36:55 +01:00

Added subscriber: @ajlanaltug

Ajlan Altug commented

2019-11-22 23:36:55 +01:00

In my case, it wouldn't even allow me to go past it. Had to turn smartscreen off temporarily :-/

Emmanuel LORANT commented

2019-11-23 08:51:09 +01:00

Ajlan, you can choose "Warn" instead of "Block" in Windows Defender settings so you can execute the file after the warning : https://media.askvg.com/articles/images6/App_Browser_Control_Windows_Defender_Security_Center.png

Anthony, I always use installer and it has always used one directory "Programs/Blender Foundation/Blender".

I tried on another computer and same thing.

Ajlan, you can choose "Warn" instead of "Block" in Windows Defender settings so you can execute the file after the warning : https://media.askvg.com/articles/images6/App_Browser_Control_Windows_Defender_Security_Center.png Anthony, I always use installer and it has always used one directory "Programs/Blender Foundation/Blender". I tried on another computer and same thing.

Anthony Edlin commented

2019-11-23 10:09:37 +01:00

I understand that previously the installer would replace the last version installed. I think with this release it is intended to be able to keep multiple versions installed. Let me check for commit...

Here is commit that changed behavior: https://developer.blender.org/rB50ad4428ac76705dc28e4cd85272a47118b6a654

Author: Lazydodo <github@lazydodo.com>
Date:   Thu Aug 15 13:43:27 2019 -0600

    Windows/MSI: Rework MSI installer.
    
    The installer always upgraded the last version installed and did not allow for two versions to be installed side by side.
    
    The reworked installer will allow side by side installs
    
    install order:
    
    2.81 -> 2.81a -> 2.82  : Allowed , will result in both 2.82 and 2.81a being installed
    2.82 -> 2.81  -> 2.81a : Allowed , will result in both 2.82 and 2.81a being installed
    2.82 -> 2.81a          : Allowed , will result in both 2.82 and 2.81a being installed
    2.82 -> 2.81a -> 2.81  : Not Allowed, 2.81 will only install if you manually remove 2.81a first.
    
    
    Do note though that this will not apply to any previously issued installers and even for 2.80a this is not something we can fix.
    
    This patch is for landing in 2.81 *only* and should be excluded from any possible 2.80a release.

I understand that previously the installer would replace the last version installed. I think with this release it is intended to be able to keep multiple versions installed. Let me check for commit... Here is commit that changed behavior: https://developer.blender.org/rB50ad4428ac76705dc28e4cd85272a47118b6a654 ``` Author: Lazydodo <github@lazydodo.com> Date: Thu Aug 15 13:43:27 2019 -0600 Windows/MSI: Rework MSI installer. The installer always upgraded the last version installed and did not allow for two versions to be installed side by side. The reworked installer will allow side by side installs install order: 2.81 -> 2.81a -> 2.82 : Allowed , will result in both 2.82 and 2.81a being installed 2.82 -> 2.81 -> 2.81a : Allowed , will result in both 2.82 and 2.81a being installed 2.82 -> 2.81a : Allowed , will result in both 2.82 and 2.81a being installed 2.82 -> 2.81a -> 2.81 : Not Allowed, 2.81 will only install if you manually remove 2.81a first. Do note though that this will not apply to any previously issued installers and even for 2.80a this is not something we can fix. This patch is for landing in 2.81 *only* and should be excluded from any possible 2.80a release. ```

Emmanuel LORANT commented

2019-11-23 11:49:05 +01:00

Thanks Anthony for explanation. Strange for the Windows Defender Smartscreen warning as last times, even by installing Blender the day of release, no warning at all.

Anthony Edlin commented

2019-11-23 17:56:12 +01:00

Changed status from 'Open' to: 'Archived'

Anthony Edlin closed this issue

2019-11-23 17:56:12 +01:00

Anthony Edlin self-assigned this 2019-11-23 17:56:12 +01:00

Anthony Edlin commented

2019-11-23 17:56:12 +01:00

Closing for now, if many more people have problems with windows defender smartscreen we can reopen.

Justin Taddei commented

2019-11-27 03:52:47 +01:00

Added subscriber: @justintaddei

Justin Taddei commented

2019-11-27 03:52:47 +01:00

I had this problem too.

Windows 10 x64 (version 1903, build 18362.476)

I had this problem too. Windows 10 x64 (version 1903, build 18362.476)

Arne commented

2019-11-30 15:35:46 +01:00

Added subscriber: @RainerWahn

Arne commented

2019-11-30 15:35:46 +01:00

Same for me. Have 2.80 installed wiith Windows 10 1903 : 18362.476. MSI installer for 2.81 is blocked as unknown app

Sriram commented

2019-12-02 11:07:47 +01:00

Added subscriber: @srius

Sriram commented

2019-12-02 11:07:47 +01:00

Um, I used steam to install blender, it didn't give me an error then. THough I did get it when I tried to install through the msi file.

Justin Taddei commented

2019-12-02 17:25:32 +01:00

Has anyone checked the hash to make sure we're actually getting the blender we think we are? I was lazy and didn't. I'll check it later today if nobody else does first.

Keith Gadberry commented

2019-12-02 17:35:04 +01:00

In #71784#822653, @justintaddei wrote:
Has anyone checked the hash to make sure we're actually getting the blender we think we are? I was lazy and didn't. I'll check it later today if nobody else does first.

Just did, it checks out. https://i.imgur.com/sGY1JZn.png
I ran the copy I just downloaded and smartscreen blocked it again.

Maybe this issue should be reopened?

> In #71784#822653, @justintaddei wrote: > Has anyone checked the hash to make sure we're actually getting the blender we think we are? I was lazy and didn't. I'll check it later today if nobody else does first. Just did, it checks out. https://i.imgur.com/sGY1JZn.png I ran the copy I just downloaded and smartscreen blocked it again. Maybe this issue should be reopened?

Ray molenkamp commented

2019-12-02 17:44:29 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2019-12-02 17:44:29 +01:00

Maybe this issue should be reopened?

it should not, there is nothing we can do on our side about smartscreen except wait for it to have enough data to trust us.

> Maybe this issue should be reopened? it should not, there is nothing we can do on our side about smartscreen except wait for it to have enough data to trust us.

Keith Gadberry commented

2019-12-02 18:02:49 +01:00

In #71784#822661, @LazyDodo wrote:
it should not, there is nothing we can do on our side about smartscreen except wait for it to have enough data to trust us.

I just tested the installer on my partner's computer, smartscreen stepped in again. There has to be a reason this is an issue when it hasn't been in the past?

Looking under properties of the 2.81 installer there is a Digital Signatures tab which shows a signature from "Stichting Blender Foundation" that the 2.80 installer doesn't have.
This is probably why it's having issues but I don't understand why it's there in the first place. ~~What's "Stichting Blender Foundation"?~~

Edit: As an American, I had to look up what a Stichting is and realize that the Blender Foundation is headquartered in the Netherlands. Still not sure why the signature is required or what it's not trusted by smartscreen. That seems like an issue that Blender Foundation should be able to remedy with Microsoft.

> In #71784#822661, @LazyDodo wrote: > it should not, there is nothing we can do on our side about smartscreen except wait for it to have enough data to trust us. I just tested the installer on my partner's computer, smartscreen stepped in again. There has to be a reason this is an issue when it hasn't been in the past? Looking under properties of the 2.81 installer there is a Digital Signatures tab which shows a signature from "Stichting Blender Foundation" that the 2.80 installer doesn't have. This is probably why it's having issues but I don't understand why it's there in the first place. ~~What's "Stichting Blender Foundation"?~~ Edit: As an American, I had to look up what a Stichting is and realize that the Blender Foundation is headquartered in the Netherlands. Still not sure why the signature is required or what it's not trusted by smartscreen. That seems like an issue that Blender Foundation should be able to remedy with Microsoft.

Ray molenkamp commented

2019-12-02 18:10:31 +01:00

Looking under properties of the 2.81 installer there is a Digital Signatures tab which shows a signature from "Stichting Blender Foundation" that the 2.80 installer doesn't have.

but yeah what happened is, we started signing all our code, so people will know the files have not been compromised and stop the 'unknown publisher: scary!' dialogs, but now smartscreen is throwing a fit, since we are a new publisher it has never seen before and will keep warning people until enough "trust is build" and naturally there is no way to check how any of that is going.... so yeah.. awesome system microsoft! top notch! loving it!

What's "Stichting Blender Foundation"?

It's the legal name of the blender foundation.

>Looking under properties of the 2.81 installer there is a Digital Signatures tab which shows a signature from "Stichting Blender Foundation" that the 2.80 installer doesn't have. but yeah what happened is, we started signing all our code, so people will know the files have not been compromised and stop the 'unknown publisher: scary!' dialogs, but now smartscreen is throwing a fit, since we are a new publisher it has never seen before and will keep warning people until enough "trust is build" and naturally there is no way to check how any of that is going.... so yeah.. awesome system microsoft! top notch! loving it! > What's "Stichting Blender Foundation"? It's the legal name of the blender foundation.

Robert Guetzkow commented

2019-12-23 01:44:48 +01:00

Added subscriber: @DrZeldaGlitch

yitzi r commented

2020-01-21 21:17:26 +01:00

Added subscriber: @WorkHard_Laugh

yitzi r commented

2020-01-21 21:17:26 +01:00

I had the same issue.

But then I went to Microsoft store and downloaded the windows 10 blender app from there and it went through with no problems.

I had the same issue. But then I went to Microsoft store and downloaded the windows 10 blender app from there and it went through with no problems. ![image.png](https://archive.blender.org/developer/F8292686/image.png)

Robert Guetzkow commented

2020-01-26 15:39:13 +01:00

Added subscriber: @JubberThe3PO