[wix-users] light.exe(0, 0): error LGHT0001: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Fri Oct 19 01:26:27 PDT 2018

Finally they (MSDN support team) asked me to go back to 1803 because something is wrong with MSI.dll in Windows 10 1809. I hope they solve it before re-release the October update.

-----Mensaje original-----
De: wix-users <wix-users-bounces at lists.wixtoolset.org> En nombre de José Ángel Martínez Torres via wix-users
Enviado el: viernes, 5 de octubre de 2018 13:28
Para: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
CC: José Ángel Martínez Torres <joseangel at digi21.net>
Asunto: Re: [wix-users] light.exe(0, 0): error LGHT0001: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

After a series of modifications to Light.exe so that it prints the names of the files to which the API MsiGetFileVersion is called, I have created a program with which I have found that if this API is called passing two particular files, in Windows 10 1809 the application crash. It does not crash if I run it in a Windows 7 or with Windows 10 1803, only with Windows 10 1809. I created an MSDN technical support ticket to inform it, I'm sure something strange happens with MSI.dll on Windows 10 1809.

-----Mensaje original-----
De: wix-users <wix-users-bounces at lists.wixtoolset.org> En nombre de Rob Mensching via wix-users Enviado el: jueves, 4 de octubre de 2018 18:48
Para: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
CC: Rob Mensching <rob at firegiant.com>
Asunto: Re: [wix-users] light.exe(0, 0): error LGHT0001: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Looks like the Win32 API ::MsiGetFileVersion() (https://docs.microsoft.com/en-us/windows/desktop/api/msi/nf-msi-msigetfileversionw) is crashing on your file. Something odd about that file?

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of José Ángel Martínez Torres via wix-users
Sent: Thursday, October 4, 2018 1:50 AM
To: wix-users at lists.wixtoolset.org
Cc: José Ángel Martínez Torres <joseangel at digi21.net>
Subject: [wix-users] light.exe(0, 0): error LGHT0001: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I'm getting the error: "light.exe(0,0): error LGHT0001: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
I started to get this error after update Windows 10 to the 1809 version.

If I run the light.exe from the console and not from within Visual Studio, the error and stack trace is the next one:

light.exe : error LGHT0001 : Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Exception Type: System.AccessViolationException

Stack Trace:
   at Microsoft.Tools.WindowsInstallerXml.Msi.Interop.MsiInterop.MsiGetFileVersion(String filePath, StringBuilder versionBuf, Int32& versionBufSize, StringBuilder langBuf, Int32& langBufSize)
   at Microsoft.Tools.WindowsInstallerXml.Msi.Installer.GetFileVersion(String filePath, String& version, String& language)
   at Microsoft.Tools.WindowsInstallerXml.Binder.UpdateFileRow(Output output, IDictionary`2 infoCache, String modularizationGuid, Hashtable fileRowIndex, FileRow fileRow, Boolean overwriteHash)
  at Microsoft.Tools.WindowsInstallerXml.Binder.UpdateFileInformation(Output output, FileRowCollection fileRows, MediaRowCollection mediaRows, IDictionary`2 infoCache, String modularizationGuid)
   at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile)
   at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)

If I create a tiny project it works correctly but with my production project, I get the error.
I've cloned the Wix3 repository and after build I tried with the light.exe located in Repos\wix3\build\debug\x86\light.exe but it freezes in the "Updating file information" stage.
I attached then the Visual Studio debugger to the light.exe process and it's unable to pause the light.exe process.

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/