fr0stbyt3

You can always roll back, but I can confirm it worked for me too.

We're working on it. I reached out my Microsoft contact as well for comments on changes related to security and this DLL. I'm hoping to hear back from them in the next day or so. If you can delay the update for now, do so. If not, please be patient. We're on it.

Is everyone getting the same error code above? Is there a stacktrace associated with this error?

I would backup main directory but all of the EXE files should do it!

To help you diagnose this: - First download a fresh copy of 1.5.1 and assure that it fails as well. - Make sure any virus protection still has an exemption for hyperspin - Post your full windows version number run winver and it'll show you

Same. I tested and both HS and HT work on 1909

We're here to help if you find an issue with 1.5.1

We obviously do not want our users reinstalling windows as a fix. I can't update my main PC to a beta release of windows, but i'll spin up a VM to see if I can reproduce later in the week. Please understand this process could be a week or two as i'm dealing with a recent death in the family. Please share any additional log files you may have in PMs if you don't want to share them directly here. Also please include the exact version of windows you're running. The insider previews are not always the same version as they roll out updates to users in batches.

The code for positioning wasn't altered between builds. So I find this quite odd. Can you link me to the theme so I can test locally?

If you could, please download a fresh copy of HS 1.5.1 and run it. In order for me to test and patch this, I need a common, reproducible test case. We normally don't put out a notice until we're able to verify there is an issue. As with most things microsoft, you shouldn't run to update windows versions the moment it comes out. The last few releases have either been pulled or have caused performance related issues. When we verify that is an issue with an RC we will make a post related to it.

Thanks for the heads up. Did you grab a clean install from the forums or did you copy an install that worked previously?

Please let use know what you find out. Sent from my Pixel 2 XL using Tapatalk

Please read above. As stated many times, it's not a virus. It's a false positive.

I've never heard of this before. Can you point me to a thread on it? Sent from my Pixel 2 XL using Tapatalk

I'll forward this on. We might need the theme files for testing. Sent from my Pixel 2 XL using Tapatalk

You have to exclude the hyperspin folder so windows defender ignores it.

Unfortunately no, we don't have 1.3.2 stable since the source has moved on since then. Can you expand on what issues you're having? Maybe open up a different thread so we don't spam this one.

Yeah, again it's a false positive. As posted above, "just set HyperSpin folder as an exclusion".

This will be resolved in the future. It has to do with how the code was compiled. Unfortunately there isn't much I can do in the current framework. Sent from my Pixel 2 XL using Tapatalk

We have you covered [emoji6] Sent from my Pixel 2 XL using Tapatalk

Impressive stuff. Ill be on touch soon. Sent from my Pixel 2 XL using Tapatalk

Yes. Simply overwrite the exe files with the ones from the update zip. Then you're good to go. Sent from my Pixel 2 XL using Tapatalk

I know this was on a change list but I forget which framework has it. I'll check with the other developer and get back to you.

Can you pm me some sample files? Sent from my Pixel 2 XL using Tapatalk

I wasn't aware of this bug. Please PM me and if you have a video of it happening, that would help greatly.