Forum Discussion
Access 2013 32 bit runtime will not install
Okay. So, background, we use 2013 32 bit access runtime for our application. On a brand new, fresh Windows 10 64 bit pro install, for whatever reason this app will no longer install. It brings up MsiExec.exe / Kernelbase.dll errors in event viewer. Trying this on windows 11 i have zero issue. Installing this on Windows 10 64 bit ver. 1809 worked. I am hoping to see if anyone has some clues for me.
I have tried installing in cmd/power
Downloaded new windows 10 64 bit may 22h2 release iso
tried different usb drives
Updated PC bios
Tried different hard drive (m.2 ssds)
Different Ram (because shooting in the dark)
Installing all updates / motherboard drivers
Here are logs:
Event Log--
Log Name: Application Source:
Application Error Date: 6/19/2024 8:54:04 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-GO2OK8Q
Description: Faulting application name: MsiExec.exe, version: 5.0.19041.3636, time stamp: 0x1c10077d
Faulting module name: KERNELBASE.dll, version: 10.0.19041.4412, time stamp: 0x6d8c3da8
Exception code: 0xe06d7363
Fault offset: 0x00140b82
Faulting process id: 0x150c
Faulting application start time: 0x01dac260e46114c8
Faulting application path: C:\Windows\syswow64\MsiExec.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 8f7103e0-fa10-44bf-bd66-77a11ba8cb5e
Faulting package full name:
Faulting package-relative application ID:
Event Xml: schemas.microsoft.com/win/2004/08/events/event "> 1000 0 2 100 0 0x80000000000000 193 Application DESKTOP-GO2OK8Q MsiExec.exe 5.0.19041.3636 1c10077d KERNELBASE.dll 10.0.19041.4412 6d8c3da8 e06d7363 00140b82 150c 01dac260e46114c8 C:\Windows\syswow64\MsiExec.exe C:\Windows\System32\KERNELBASE.dll 8f7103e0-fa10-44bf-bd66-77a11ba8cb5e
System Info--
System Information report written at: 06/19/24 08:56:58
System Name: DESKTOP-GO2OK8Q
[System Summary]
Item Value
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-GO2OK8Q
System Manufacturer ASUS
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor 13th Gen Intel(R) Core(TM) i5-13500, 2500 Mhz, 14 Core(s), 20 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1658, 5/22/2024
SMBIOS Version 3.5
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product PRIME Z790-P WIFI D4
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
User Name DESKTOP-GO2OK8Q\admin
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.7 GB
Available Physical Memory 13.0 GB
Total Virtual Memory 18.6 GB
Available Virtual Memory 16.1 GB
Page File Space 2.88 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
[Hardware Resources]
[Conflicts/Sharing]
Resource Device
Memory Address 0x85F00000-0x85F03FFF Standard NVM Express Controller
Memory Address 0x85F00000-0x85F03FFF PCI Express Root Port
3 Replies
Josh_Vodden , i am not familiar with runtime x32 being installed to x64 os, have you done it before?
- I currently have exactly that configuration running. I did install the newer version of the runtime, so maybe A2013 runtime is not compatible, which I would tend to doubt.
Otherwise, it's not all that different from running full Access 32 bit on a 64bit OS.
Trying to interpret the reported error log, it sounds to me more likely to be a borked install of Windows than a problem with the runtime. But, I am not well enough informed on Windows installs to wade into that water.- I agree with George. At the very least you should run DISM to ensure that Windows is OK.
https://www.dell.com/support/kbdoc/en-us/000122035/how-to-use-the-deployment-image-servicing-and-management-tool-dism-to-repair-the-windows-system-store
