I am wondering if you can help me. I just installed the windows 64 bit version, I updated my Java to the latest version. Rebooted my computer and on attempted to open datawarrior the following two messages keep appearing. Wondering if you could suggest any possible fixes to this problem.

I assume, you installed the 32-bit Java JRE, because this is the default even for an 64 bit Windows installation.
Oracle says on its web site that 64-bit Internet Explorer still has problems to render all web sites. Therefore,
Microsoft installs the 32-bit version of IE as default, which forces Oracle to supply 32-bit Java as default.
The 64 bit installation is a little difficult to find on the Java download web site. But you can install both, 32-bit and 64-bit JREs independently. You may install the 64-bit JRE for Windows after the DataWarrior installation to fix the issue. The following seems to be a link to the most recent 64-bit WIndows JRE:

I have been running DW on windows 10 for some time without incident, however recently (without any known change to software) began getting the same java.dll and runtime errors described above. After reinstalling 64 bit java and 64 bit dw, the program opens and runs fine, however upon restarting the machine, I get the same errors again.

I assume that some other software has installed a 32-bit Java environment and made it the preferred one.
If you type 'java -version' in a cmd window, you should see, whether you use a 32- or 64-bit version of the JRE.
If you see something like 'Java HotSpot(TM) 64-Bit Server VM', then you have a 64 bit JRE. If you don't
find '64 Bit' in the output, then you have a 32-bit Java installation.

Hi Thomas, thanks for the reply. Java version responds with java se runtime environment and java hotspot 64-bit server VM. There is no other version of java installed. After a fresh java install, the app works fine, but after restarting, the same java errors come up again. I'd appreciate any other suggestions. Regards, Jamie

Hi Jamie, it is hard for me to give a reasonable advise. It seems that your Java environment is damaged after a restart. You may confirm that by running another other Java application after restart from the command line. You may try the molviewer.jar attached to this message. Try running it by typing the following in a cmd window: java -jar molviewer.jar
If this works after a fresh java install, but doesn't after reboot, then you need to check, what destroys your java installation during reboot. If it works after reboot, quite honestly I have no clue at the moment. Thomas

I have been running DW on windows 10 for some time without incident, however recently (without any known change to software) began getting the same java.dll and runtime errors described above. After reinstalling 64 bit java and 64 bit dw, the program opens and runs fine, however upon restarting the machine, I get the same errors again.

any suggestions?

Same situation here - DW working fine with Win10 x64 until a few weeks ago.
I have temporarily solved the problem by installing the latest 64b Java runtimes.
Just a few days ago however, Java seems to "disappear" for no apparent reason after a few hours of installation.

@Jsimpson; Is your Windows-environment managed with eg SCCM?
I'm thinking if it isn't, then it's not a SCCM issue, but rather a Windows 10-problem.