Stewart X Addison

I think I've just hit the same problem ...

Initial thoughts is that this is going to have been a result of [switching the build up to VS2019](https://github.com/adoptium/temurin-build/pull/2992). @toshiona was the previous GA level 11.0.15 ok for you?

Thanks for confirming - we're going to build 11.0.16 with the earlier visual studio for now to mitigate this.

Looks like https://github.com/adoptium/temurin-build/pull/2967 has bumped it to VS2017. We should also consider the implications for the 32-bit JDK8 builds which I understand do not work with VS2017 based on a...

@karianna This has not been implemented. Slightly worryingly the [64-bit JDK8 build logs](https://ci.adoptopenjdk.net/view/Failing%20Temurin%2jobs/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-temurin) currently show this: ``` 19:08:02 Tools summary: 19:08:02 * Environment: cygwin version 3.1.7(0.340/5/3) (root at /cygdrive/c/cygwin64) 19:08:02...

My preference would very much be not to change it at this stage of the process - I mostly highlighted it just so tha people didn't think it had happened.

Adoptium doesn't do any 32-bit builds other than on Windows and ARM Linux, although I'd be surprised if your issue was related to it being 32-bit. It's definitely possible to...

@k7295 Did you manage to resolve this? Have you tried copying the files from `jre/lib/security` from the adoptium ones into the same location on your self-build JDK?

Interesitng that it's only been failing since the 27th August - the same test appears to have been run successfully in the earlier versions.

Ah - the passingone was on a Windows 2019 macine `test-azure-win2019-x64-1` whereas it looks like it might be failing on the 2012 ones