dotnet: .NET Framework 4.7.2 Developer Pack installer crashes when run over WinRM

When running the .NET Framework 4.7.2 Developer Pack installer (NDP472-DevPack-ENU.exe) over WinRM, the installer crashes. It does not crash when run from an interactive desktop session.

This can be reproduced by using Packer from Hashicorp, or Powershell Remoting, on a clean installation of Windows Server 2012 R2.

The installer exits with an exit code corresponding to 0xC0000005, which represents an Access Violation.

The only clue is a single entry in the Application event log:

Faulting application name: NDP472.exe, version: 4.7.3081.0, time stamp: 0x59074750
Faulting module name: wixstdba.dll, version: 3.11.1701.0, time stamp: 0x59074755
Exception code: 0xc0000005
Fault offset: 0x0000132e
Faulting process id: 0x4a4
Faulting application start time: 0x01d42eb0851f726b
Faulting application path: C:\Users\ADMINI~1\AppData\Local\Temp\{3A52AFB4-9AC4-4B14-969F-83984D4F2CFC}\.cr\NDP472.exe
Faulting module path: C:\Users\ADMINI~1\AppData\Local\Temp\{46D19905-2499-4730-B543-FD59D5BE394C}\.ba\wixstdba.dll
Report Id: 009dd28b-9aa4-11e8-80b4-00155dc51fc5
Faulting package full name: 
Faulting package-relative application ID: 

System event logs: NDP472-diag-evtlogs.zip

Contents of user’s %TEMP% folder: NDP472-diag-usertemp.zip

X-ref Microsoft Partner Support, case [REG:118080918754010].

See also: https://twitter.com/yaakov_h/status/1027050943441858560

About this issue

  • Original URL
  • State: open
  • Created 6 years ago
  • Comments: 21 (7 by maintainers)

Most upvoted comments

The Chocolatey package works around this problem by recognizing that specific exit code and checking whether the SDK got actually installed. Perhaps the Visual Studio installer does something similar.