# Application unable to start correctly (0xc0000142) error

**URL:** <https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410>\
**Category:** Support\
**Created:** [September 12, 2019, 9:27pm UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410 "2019-09-12T21:27:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [September 12, 2019, 9:27pm UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410/1 "2019-09-12T21:27:23Z")

</div>

I just downloaded and installed (into my user space) Slicer nightly. I ended up getting this error message. I already tried uninstall and reinstalled (to different locations) a bunch of times as generic help for this error code suggests on web.

![slicer_start_error](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/7/c/7cfa2317812e6b3684d29e4cb8d2476c1e36880e.png).

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [September 12, 2019, 9:31pm UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410/2 "2019-09-12T21:31:19Z")

</div>

I can provide info that I downloaded today’s nightly for Windows and it started normally for me.

---

<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:** [September 12, 2019, 9:36pm UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410/3 "2019-09-12T21:36:55Z")

</div>

Today’s Preview Release works well for me, too.

Have you installed any new software recently? Do previous Slicer releases work well?

See troubleshooting information here: [https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/Troubleshooting#Instruction\_for\_Windows](https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/Troubleshooting#Instruction_for_Windows)

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [September 13, 2019, 1:53am UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410/4 "2019-09-13T01:53:38Z")

</div>

This was a windows 7 computer with a working Slicer that was recently migrated to Windows 10. It must be some sort of a corporate user policy change that probably broke the functionality. I managed to install other new programs (e.g., TurboVNC etc) that all seem to work.

It will be hard to chase, so I will just have them do a fresh reinstall of OS.

---

<div class="post-metadata">

**Author:** ![evan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/evan/32/4953_2.png) [@evan](https://discourse.slicer.org/u/evan)\
**Post date:** [September 20, 2019, 3:09pm UTC](https://discourse.slicer.org/t/application-unable-to-start-correctly-0xc0000142-error/8410/5 "2019-09-20T15:09:48Z")

</div>

I also experienced this error on the 4.11.0-2019-09-03 and 4.11.0-2019-09-17 slicer nightlies. Attempted the following with no avail:

- Two different Windows 10 machines (both 3rd generation Intel)
- Installing to a custom directory
- Installing to the default suggested directory
- Opening as administrator
- Opening with the ‘–disable-settings’ flag

I was however able to install and run both nightly versions without error on a Linux machine (7th gen Intel).

Edit: After reading the [post linked above](https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175/26), I see now it is a CPU support issue.