Bottom-line up front: Abaqus subroutines link, but Standard.exe fails even with a modified environment file. Is there another workaround, or are we doing something wrong?

System information: 

• Abaqus 2021
• Visual Studio Community 2022
• Intel OneAPI 2024.1
• Linker version: 14.39.33523.0
• Fortran compiler version: 2021.12

Problem description: 

After following the installation procedure for Abaqus with subroutine capability (QA00000069459), the compilers appear to link and the environment variables are initialized. The correct linker and fortran compilers are displayed (I'll spare the screenshot, but the relevant system information is shown above). 

However, the verification job for user subroutines in Standard.exe fails, with nothing printed to the log file. This is reminiscent of the OneAPI bug that requires the following line be added to the abaqus_v6.env environment file:

link_sl='LINK /NODEFAULTLIB:LIBCMT.LIB /dll /def:%E /out:%U %F %A %L %B'

Unfortunately, this modification doesn't remedy the issue; the solver aborts immediately. 

Troubleshooting steps taken:

• Verified environment variables are set correctly for the compilers (running via the OneAPI compiler environment command prompt, thanks @RM for the video!).

• Executed the verification job in debug mode: 

  abaqus -debug -standard -j std_user -user std_user	

• This confirmed that the compilers were linked and properly communicating, as it opened the visual studio debugger. Upon executing the subroutine in debug mode, the error is 'Entry Point Not Found.' From a few google searches, this seems as though standard.exe cannot find a dll (specifically, standard.exe fails to find ntdll.dll), but I don't know where to go from there. 
• Modifying the environment file produces the same result.

The question(s):

• The abaqus_v6.env was modified, but didn't seem to change the result. Are we modifying the wrong environment file, or doing something else wrong on that side?
• Assuming the environment file is modified correctly, is there a possibility that the VS Community edition needs another fix?
• Is there anything else we can do to track down this error, short of uninstalling and re-installing or obtaining a full visual studio license?

Thanks in advance for your time. My colleague (@JF ) and I have spent the last few weeks trying a variety of different things, but we keep coming back to the same problem. I'm really hoping it's an easy fix and a mistake on our part with respect to the environment file modification.