# Windows 10-3 nightly build with Windows Security issues

**URL:** <https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002>\
**Category:** Development\
**Created:** [October 4, 2021, 7:51pm UTC](https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002 "2021-10-04T19:51:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hherhold](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hherhold/32/12199_2.png) [@hherhold](https://discourse.slicer.org/u/hherhold)\
**Post date:** [October 4, 2021, 7:51pm UTC](https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002/1 "2021-10-04T19:51:32Z")

</div>

99% of the time, I use Slicer on a Mac, so 1000 apologies if this is something obvious.

I downloaded the latest nightly on my Windows machine (Windows 10) and I get a ton of “This content is blocked” errors when I try to run it or even go to the directory with Slicer.exe in it.

Anybody else run into this? I have recently run windows update and everything should be up to date. Note that I do not have Admin on this machine and cannot tell these warnings to just go away.

Thanks!!

-Hollister

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [October 4, 2021, 8:17pm UTC](https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002/2 "2021-10-04T20:17:35Z")

</div>

Thanks for the report 🙏

> [@hherhold](#):
>
> I get a ton of “This content is blocked” errors when I try to run it or even go to the directory with Slicer.exe

This is likely explained by the fact we do not sign the preview build.

Do you get similar message with other builds ?

To obtain older build, you can use URL like the following: [https://download.slicer.org/?offset=-4](https://download.slicer.org/?offset=-4)

---

<div class="post-metadata">

**Author:** ![hherhold](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hherhold/32/12199_2.png) [@hherhold](https://discourse.slicer.org/u/hherhold)\
**Post date:** [October 4, 2021, 8:25pm UTC](https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002/3 "2021-10-04T20:25:14Z")

</div>

The only other build I have on this machine is months old (May or June nightly build) and it runs fine. I’ll try to download a more recent one and see what happens.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [October 5, 2021, 6:33pm UTC](https://discourse.slicer.org/t/windows-10-3-nightly-build-with-windows-security-issues/20002/4 "2021-10-05T18:33:48Z")

</div>

During the expected (admittedly somewhat annoying process) of installing a Slicer Preview Release on Windows (downloaded using Edge browser) requires you to confirm 3 times (each time with two clicks) that you indeed want to install Slicer:

- Click the download link and wait for the download to complete
- **Click on “…” button of the downloaded item, click "Keep"**
- **Click “Show more”, click “Keep anyway”** and wait for the automatic scan to complete (may take 10-20 seconds)
- **Click on the installer, click “More info”, click "Run anyway"**
- Click through the installer (Next/Agree/Install)

This does not happen with the signed installer, but we only sign the Slicer Stable Release.