2.Download a new setup file from here: Downloads, put it into a new clean folder, reboot your machine, run it as administrator, wait for VS finishes installing.

3.Launch VS and keep the default settings then check if the same error appears.

If the same error appears, please open VS Developer Command Prompt, run devenv /log command, navigate to %AppData%\Microsoft\VisualStudio\17.0_<UniqueID> folder, and search for ActivityLog.xml file, share(avoid the privacy information) the ActivityLog.xml file with us to check further.

Besides, if it’s possible, I may suggest you try to install and use VS 2019 just as a temporarily workaround.

Sincerely,

Tianyu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

While trying to resolve the error that occurred during compilation, I applied the solution suggestions I found on the internet, but I couldn’t completely fix the issue. Therefore, I wanted to share this post to assist others who may encounter the same error.

When I started the compilation such an error message appeared on the screen.

Firstly, go to Tools -> NuGet Package Manager -> Package Manager Console.

In the Package Manager Console that opens, type the commands that appear in the screenshot respectively. dotnet restore dotnet build

After doing that carefully, and compiling your project, it should run without any errors.

By the way, in the same header file the variables in the string type have been defined before but they are OK. It is interesting because the error only occurs when I try to add new variable in "string" type.

• 2023-11-16T10:26:42.2666667+00:00 This message occurs:
• 
  RLWA32 40,021 Reputation points 2023-11-16T10:38:13.7366667+00:00 Anything relevant in the event log after trying outside of VS? Run dumpbin /headers on the .exe and post the output. Do it from a visual studio developer command prompt.
• 2023-11-16T11:05:45.3433333+00:00 Nothing
• 
  RLWA32 40,021 Reputation points 2023-11-16T11:21:57.24+00:00 What about dumpbin output?
• 2023-11-16T12:02:22.5666667+00:00 Dump of file QEGTRAIN.exe File Type: EXECUTABLE IMAGE Summary

      1000 .00cfg  
  79CFC000 .data  
     14000 .idata  
     1F000 .pdata  
     6B000 .rdata  
      6000 .reloc  
      1000 .rsrc  
    20E000 .text  
  

• 
  RLWA32 40,021 Reputation points 2023-11-16T12:11:55.1233333+00:00 It looks like you forgot to specify the /headers option.
• 
  RLWA32 40,021 Reputation points 2023-11-16T12:34:28.78+00:00 Now remove the string variable declaration and create a working version of your debug build. Run dumpbin /headers on the working version and post that output. I expect it will differ significantly from the previous post.
• 2023-11-16T12:56:22.0966667+00:00

  Dumpbin output for Working version

  FILE HEADER VALUES

          8664 machine (x64)  
             8 number of sections  
      65561038 time date stamp Thu Nov 16 13:51:04 2023  
             0 file pointer to symbol table  
             0 number of symbols  
            F0 size of optional header  
            22 characteristics  
                 Executable  
                 Application can handle large (>2GB) addresses  
  

  OPTIONAL HEADER VALUES

           20B magic # (PE32+)  
         14.37 linker version  
        20D400 size of code  
      72E73C00 size of initialized data  
             0 size of uninitialized data  
          5961 entry point (0000000140005961) @ILT+18780(mainCRTStartup)  
          1000 base of code  
     140000000 image base (0000000140000000 to 00000001B3085FFF)  
          1000 section alignment  
           200 file alignment  
          6.00 operating system version  
          0.00 image version  
          6.00 subsystem version  
             0 Win32 version  
      73086000 size of image  
           400 size of headers  
             0 checksum  
             3 subsystem (Windows CUI)  
          8160 DLL characteristics  
                 High Entropy Virtual Addresses  
                 Dynamic base  
                 NX compatible  
                 Terminal Server Aware  
     2540BE400 size of stack reserve  
      3B9ACA00 size of stack commit  
      3B9ACA00 size of heap reserve  
      3B9ACA00 size of heap commit  
             0 loader flags  
            10 number of directories  
             0 [       0] RVA [size] of Export Directory  
      7306CB70 [     104] RVA [size] of Import Directory  
      7307F000 [     43C] RVA [size] of Resource Directory  
      7304B000 [   1B840] RVA [size] of Exception Directory  
             0 [       0] RVA [size] of Certificates Directory  
      73080000 [     F34] RVA [size] of Base Relocation Directory  
        24FE40 [      38] RVA [size] of Debug Directory  
             0 [       0] RVA [size] of Architecture Directory  
             0 [       0] RVA [size] of Global Pointer Directory  
             0 [       0] RVA [size] of Thread Storage Directory  
        24FCC0 [     140] RVA [size] of Load Configuration Directory  
             0 [       0] RVA [size] of Bound Import Directory  
      7306A000 [    2B70] RVA [size] of Import Address Table Directory  
             0 [       0] RVA [size] of Delay Import Directory  
             0 [       0] RVA [size] of COM Descriptor Directory  
             0 [       0] RVA [size] of Reserved Directory  
  

  SECTION HEADER

  1

  .text name 20D2ED virtual size

  1000 virtual address (0000000140001000 to 000000014020E2EC)  
  

  20D400 size of raw data

   400 file pointer to raw data (00000400 to 0020D7FF)  
     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  60000020 flags

       Code  
       Execute Read  
  

  SECTION HEADER

  2

  .rdata name 6ACCC virtual size 20F000 virtual address (000000014020F000 to 0000000140279CCB) 6AE00 size of raw data 20D800 file pointer to raw data (0020D800 to 002785FF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  40000040 flags

       Initialized Data  
       Read Only  
  

  Debug Directories

      Time Type        Size      RVA  Pointer  
   - --    
  65561038 cv            58 00254620   252E20    Format: RSDS, {7AAD8441-161A-48E7-B402-A4F30053B2E3}, 1, C:\Users\kkeskin\Documents\EGTrain_Kemal\x64\Debug\QEGTRAIN.pdb  
  65561038 feat          14 00254678   252E78    Counts: Pre-VC++ 11.00=0, C/C++=87, /GS=87, /sdl=0, guardN=44  
  

  SECTION HEADER

  3

  .data name 72DD0DB1 virtual size 27A000 virtual address (000000014027A000 to 00000001B304ADB0)

  2A00 size of raw data  
  

  278600 file pointer to raw data (00278600 to 0027AFFF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  C0000040 flags

       Initialized Data  
       Read Write  
  

  SECTION HEADER

  4

  .pdata name 1E570 virtual size 7304B000 virtual address (00000001B304B000 to 00000001B306956F) 1E600 size of raw data 27B000 file pointer to raw data (0027B000 to 002995FF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  40000040 flags

       Initialized Data  
       Read Only  
  

  SECTION HEADER

  5

  .idata name 130E4 virtual size 7306A000 virtual address (00000001B306A000 to 00000001B307D0E3) 13200 size of raw data 299600 file pointer to raw data (00299600 to 002AC7FF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  40000040 flags

       Initialized Data  
       Read Only  
  

  SECTION HEADER

  6

  .00cfg name

   175 virtual size  
  

  7307E000 virtual address (00000001B307E000 to 00000001B307E174)

   200 size of raw data  
  

  2AC800 file pointer to raw data (002AC800 to 002AC9FF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  40000040 flags

       Initialized Data  
       Read Only  
  

  SECTION HEADER

  7

  .rsrc name

   43C virtual size  
  

  7307F000 virtual address (00000001B307F000 to 00000001B307F43B)

   600 size of raw data  
  

  2ACA00 file pointer to raw data (002ACA00 to 002ACFFF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  40000040 flags

       Initialized Data  
       Read Only  
  

  SECTION HEADER

  8

  .reloc name

  5E58 virtual size  
  

  73080000 virtual address (00000001B3080000 to 00000001B3085E57)

  6000 size of raw data  
  

  2AD000 file pointer to raw data (002AD000 to 002B2FFF)

     0 file pointer to relocation table  
     0 file pointer to line numbers  
     0 number of relocations  
     0 number of line numbers  
  

  42000040 flags

       Initialized Data  
       Discardable  
       Read Only  
  

  Summary

      1000 .00cfg  
  72DD1000 .data  
     14000 .idata  
     1F000 .pdata  
     6B000 .rdata  
      6000 .reloc  
      1000 .rsrc  
    20E000 .text  
  

• 
  RLWA32 40,021 Reputation points 2023-11-17T06:32:21.4133333+00:00 I was hoping that dumpbin output would help identify why Windows believes that VS2022 is producing an invalid image. I don't know how much memory (physical and virtual) your system has but I noticed memory reserve and commit settings for stack and heap that far exceed linker defaults. At this point I suggest you open a case with Microsoft through Visual Studio's feedback mechanism to report a problem.

2023-11-21T10:39:29.4233333+00:00

At this point I suggest you open a case with Microsoft through Visual Studio's feedback mechanism to report a problem.

Thank you @RLWA32 . Microsoft Visual Studio's feedback mechanism can be slow for us to solve it. Do you know of any contact at Microsoft who I can forward this problem directly? @Anna Xiu-MSFT