Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, May 29, 2017 7:20 AM
Issue Details:
Hardware: DELL Latitude E6540
OS: Windows 10 (german)
VS-Version: Visual Studio 2015 with Update 3 (english)
prepare to reproduce:
- Fresh installation of Windows 10 image
- install Vs 2015 without any reported problems.
- Start Vs 2015 no reported problems
Steps to reproduce:
- Start VS 2015
- New project --> C++,MFC, MFC-Application (all default values)
- Build project --> Error: "LINK : fatal error LNK1327: failure during running mt.exe"
or
- Start VS 2015
- New project --> C++,ATL, ATL-Dll (all default values)
- Build project --> Error: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(1318,5): error MSB6006: "midl.exe" exited with code -1073741819
Report.wer contains the following:
Version=1
EventType=APPCRASH
EventTime=131399317076639364
ReportType=2
Consent=1
UploadTime=131405132861834713
ReportIdentifier=cfb59ea9-3eee-11e7-9d82-80000b638615
IntegratorReportIdentifier=a536cf99-804f-4766-a65c-a184b4f27f1d
WOW64=1
NsAppName=mt.exe
AppSessionGuid=00003b08-0001-000e-cbd0-dc91fbd2d201
TargetAppId=W:0006d6338daa86cba503d16c85b9a654261500000904!00004de350e27fbe41f2f45decf70ac30b76046d8641!mt.exe
TargetAppVer=2015//02//27:01:24:18!f2193!mt.exe
BootId=4294967295
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=mt.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=6.3.9600.17336
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=54efc742
Sig[3].Name=Fehlermodulname
Sig[3].Value=dgapi.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=7.3.0.1021
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=58937906
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=00043833
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=658c
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=658c5b10bf6dac71bf33c5470aab5cba
UI[2]=C:\Program Files (x86)\Windows Kits\8.1\bin\x86\mt.exe
UI[3]=mt2.exe funktioniert nicht mehr
UI[4]=Windows kann online nach einer Lösung für das Problem suchen.
UI[5]=Online nach einer Lösung suchen und das Programm schließen
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=C:\Program Files (x86)\Windows Kits\8.1\bin\x86\mt.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=c:\windows\system32\dgapi.dll
LoadedModule[5]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[6]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[7]=C:\WINDOWS\System32\USER32.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[9]=C:\WINDOWS\System32\win32u.dll
LoadedModule[10]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[11]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[12]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[13]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[14]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[15]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[16]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[17]=C:\WINDOWS\System32\sechost.dll
LoadedModule[18]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[19]=C:\WINDOWS\System32\ole32.dll
LoadedModule[20]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[21]=C:\WINDOWS\System32\combase.dll
LoadedModule[22]=C:\WINDOWS\System32\profapi.dll
LoadedModule[23]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[24]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[25]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[26]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[27]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[28]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[29]=C:\WINDOWS\System32\shcore.dll
LoadedModule[30]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[31]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[33]=C:\Program Files (x86)\MSBuild\12.0\bin\FileTracker.dll
LoadedModule[34]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[35]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[36]=C:\Program Files\DGAgent\plugins\09D849B6-32D3-4A40-85EE-6B84BA29E35B\AE_MailSensor_Plugin.dll
LoadedModule[37]=C:\Program Files\DGAgent\plugins\09D849B6-32D3-4A40-85EE-6B84BA29E35B\ame_outlooksensor.dll
LoadedModule[38]=C:\Program Files\DGAgent\plugins\09D849B6-32D3-4A40-85EE-6B84BA29E35B\ame_smtpsensor.dll
LoadedModule[39]=C:\Program Files\DGAgent\plugins\8E4EA70A-6128-4B57-BD3F-8E9E0F0DA6BB\OS_Plugin.dll
LoadedModule[40]=C:\Program Files\DGAgent\plugins\8E4EA70A-6128-4B57-BD3F-8E9E0F0DA6BB\COM_Sensor.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=mt2.exe
AppPath=C:\Program Files (x86)\Windows Kits\8.1\bin\x86\mt.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=9D6AD8D0A341E42B76C8B15E1EEB93E8
MetadataHash=-30701919
All replies (5)
Tuesday, May 30, 2017 5:36 AM
Hi meinolf freiburg,
Welcome to the MSDN forum.
Refer to your description, I created the new MFC application and ATL project to test and successfully build them.
Please go to Control Panel-Programs and Features, right click the VS 2015 and Change-Modify, confirm the components ‘Common Tools for Visual C++ 2015’, ‘Microsoft Foundation Classes for C++’, ‘Windows XP Support for C++’ that under ‘Visual C++’ already checked like the following, if not, please check it to update.
>>Build project --> Error: "LINK : fatal error LNK1327: failure during running mt.exe"
Please right click the MFC application and choose ‘Properties’ and check the target platform version, the default value is ‘8.1’ on my side.
I tried to change the target platform version like ’10.0.15063.0’ and build it, the result is failed with the similar error like cannot run ‘rc.exe’, then I copied the ‘rc.exe’ and ‘rcdll.dll’ from C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64 and paste them into C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin, then build it again, now meet another new error cannot run the ‘mt.exe’, then I copied the ‘mt.exe’ like before, finally the build is successful.
Please have a look at this similar issue: Visual Studio can't build due to rc.exe and have a try on your side, copy those required files from the target SDK version installation location to VS 2015 VC installation folder.
Meanwhile, there have another similar issue: Fatal error cannot run 'mt.exe' at compiling VS 2012 C++ project to Set "Generate manifest" as No in Linker.
Best regards,
Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Tuesday, May 30, 2017 6:09 AM
Hi Sara,
tried to copy mt.exe to VC/bin directory. This doesn't change the issue.
With Setting "Generate manifest" to "No" the solution compiled, but it's not an option for me because of company regulations.
Best regards
Meinolf
Wednesday, May 31, 2017 8:06 AM
Hi Meinolf,
Thank you for your update.
Have you tried to change the target platform version? Or what's your current target platform version?
Meanwhile, you can go to Control Panel-Programs and Features, right click the VS 2015 and Change-Repair to repair VS 2015, then test this issue again.
Best regards,
Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Friday, June 2, 2017 7:16 AM | 2 votes
Hi Sara,
problem was caused by "Digital Gardian"-Software.
Solved by our Security-Team.
Regards
Meinolf
Friday, June 2, 2017 7:37 AM
Hi Meinolf,
I'm so glad to hear that your issue is solved and thank you for your sharing.
BTW, please mark your solution as answer and that can help other community members meet the same or similar issue to easier search this helpful solution, thank you for your cooperation.
Best regards,
Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].