# Issues with Intel Fortran in Visual Studio **URL:** \ **Category:** Uncategorized\ **Created:** [January 5, 2022, 3:46pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536 "2022-01-05T15:46:36Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![mkonecny](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/mkonecny/32/1022_2.png) [@mkonecny](https://fortran-lang.discourse.group/u/mkonecny)\ **Post date:** [January 10, 2022, 5:39pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/21 "2022-01-10T17:39:40Z")
I’ve already spent hours trying to solve this. I guess I could write to the Intel forum, but as there are other things I dislike about Visual Studio, my primary goal is to get them to support vscode debugging, so I’ll be doing that first… Good to hear about improvements in VS2022. I can’t do it whenever I like because the whole team has to do it, but I guess we’ll be switching soon (this year). ---
**Author:** ![CRquantum](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/crquantum/32/730_2.png) [@CRquantum](https://fortran-lang.discourse.group/u/CRquantum)\ **Post date:** [January 10, 2022, 5:42pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/22 "2022-01-10T17:42:29Z")
I see. I found sometimes it may be related with Windows SDK version. ![image](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/2X/f/fd4dd17f06ac5ebd248395d2baca249a42823acf.png) The latest version of SDK may help. ---
**Author:** ![mkonecny](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/mkonecny/32/1022_2.png) [@mkonecny](https://fortran-lang.discourse.group/u/mkonecny)\ **Post date:** [April 1, 2022, 2:57pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/23 "2022-04-01T14:57:01Z")
I wrote a plea to Intel asking to create a vscode debugger extension. See this post for details: > [@A plea to Intel to supply vscode debugging on Windows](https://fortran-lang.discourse.group/t/a-plea-to-intel-to-supply-vscode-debugging-on-windows/3098): > > I feel like support for ifort-built Windows binaries debugging in vscode is long overdue. I have tried to explain my reasons here in a sort of a plea to Intel to maybe get things going in the right direction: Would be great if anyone who feels the same way could support the request by upvoting or commenting on the issue on the Intel forum so that it gains some traction. Also, let me know what you think (preferrably on the Intel forum, though). Thanks! ---
**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\ **Post date:** [September 6, 2022, 6:30pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/24 "2022-09-06T18:30:25Z")
I’m starting to use MS Visual Studio for the first time to debug a large Fortran application for Windows. It just happened so that VS 2022 version 17.2 which was the latest version at the time of my download (early August) broke compatibility with the Intel Fortran compiler suite: > **[VS 2022 Version 17.2 and Intel Fortran Integration](https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/vs2022-version-17-2-and-intel-fortran-integration.html)** > > This update to VS 2022, the 17.2 update, will break the Intel Fortran Integrations into Visual Studio. I’m now installing VS 2022 v17.0 and hope that it will work. Not exactly on-topic to the original question, but FWIW, I hope it helps somebody here. It took me a while to realize that it wasn’t me but VS that was causing the problem, because the error message was cryptic. ---
**Author:** ![mkonecny](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/mkonecny/32/1022_2.png) [@mkonecny](https://fortran-lang.discourse.group/u/mkonecny)\ **Post date:** [September 6, 2022, 7:11pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/25 "2022-09-06T19:11:05Z")
My colleague recently ran into the same issue by accidentally updating VS. The issue should be fixed from VS 17.3.0 onward, see this post: > **[VS 2022 v17.2.x breaks Intel Fortran, use v17.3.2 and newer](https://community.intel.com/t5/Intel-Fortran-Compiler/VS-2022-v17-2-x-breaks-Intel-Fortran-use-v17-3-2-and-newer/m-p/1382358)** > > Update 9 August 2022:   The information, errors, workarounds are for older VS 2022 v17.2.x.  As of 9 August 2022 Visual Studio 2022 v17.3 was released which fixes this issue. UPGRADE VS2022 to v17.3.0 or newer   OLDER 17.2.X... ---
**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\ **Post date:** [September 6, 2022, 7:42pm UTC](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536/26 "2022-09-06T19:42:17Z")
> [@mkonecny](#): > > The issue should be fixed from VS 17.3.0 onward, see this post: Confirmed, it now works with both VS 17.0.13 and 17.3.3. I wish I had seen that post sooner. When installing VS 17.0.13, I had to run the Repair sequence for the Intel compiler suite (v2022.1.0) for it to get integrated with the IDE. [Previous page](https://fortran-lang.discourse.group/t/issues-with-intel-fortran-in-visual-studio/2536.md?page=1)