Publishing experiences can be painful

My organization blocks a lot of things on my system, so I want to share the different things I was going through to get ThingWorx Studio to work. We are working on Windows 10.

1. We use app-locker to lockout several system-directories and each application which want to run out of these directories have to be unlocked by our system-admins So be sure that "ThingWorx Studio.exe" and "node.exe" are unlocked in C:\Users\<username>\AppData\Local\Apps\2.0\<id:1><id:2>\thin..udio_<id:3>\ where the id's are random numbers.
2. Make sure that your CAD-converter tools also are unlocked. They are located in C:\Users\<username>\AppData\Roaming\ThingworxStudio\studio-download.vuforia.io\node_modules\cad-import-filters and underlying directories
3. Uploading data from internal network was blocked by the firewall, so make sure you can upload your data.
4. When you are using Direct Access outside your company, you're traffic is going through the firewall of the company and is also blocked.So check if you are allowed to upload data.

ThingWorx Studio doesn't give any clues, even with point 3 and 4 it says that the experience was published successfully, but nothing was shown after the ThingMark was scanned.

So hopefully this will help you to make publishing an experience a nice experience