KB2918614 breaks Windows Installer Service

Anonymous

I didnt know where best to post a bug report about KB2918614.

This is for Windows 8.1 Pro

It appears on August 13 I received KB2918614 and immediately after I began having trouble with certain MSI installations, especially those that required any version of Visual C++ Redistributable to be installed.

Now, of course I have most of those already installed, but the install process of many programs runs those redistributables before the actual install runs. It would always give me the error of "key not valid for use in specified state" and exit with a 1603 event.

I didnt know what caused the problem at the time and went through many troubleshooting steps including sfc/scannow, registry modifications (which have all been switched back to their original values), and attempts at re-installing the Windows Installer Service for Windows 8.1 (5.0) which apparently does not have its own redistributable install file.

Eventually I determined that I received a large number of updates on 8/13, so I removed them all. This immediately fixed my problem.

As I didnt know if that was a fluke and I didnt know which specific update caused the problem, on reboot they all re-installed.

The problem returned as soon as I started back into windows.

I went through each of the knowledgebase articles and located KB2918614 as being the only one that modifies the MSI Windows installer service files.

I have now removed and hidden this update.

I wanted to notify Microsoft of this issue but did not know the best method to do so, so I am posting it in the Microsoft community in the event another user has the same problem as I did in order to work around it.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

105 answers

Anonymous

2014-09-08T21:21:54+00:00

Hi,

i also see issue with this update on Win2k8 R2 SP1 machines ,which using a mandatory roaming profile. After installing this "fix" all my machines where unable to install MSI packages. it has a error " the profile for the user is a temporary profile". i've start digging and was able to install the SW only after removing this "fix" - obviously it has issues.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-09T01:26:23+00:00

Can you get your file associations and paste the here? Open a command prompt > assoc > right click the command prompt and choose select all then press enter to copy.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-09T06:15:38+00:00

Hi DanzIZme,

OK, here are the links to the two files you requested -

File Associations: http://1drv.ms/1tpv212

WindowsUpdate.log: http://1drv.ms/YsnphB

Hopefully, these will point to SOMETHING I can do to resolve this.

Thanks for your help.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-09T14:16:24+00:00

Same problem here with KB2918614 ! Since it's installed on computers (Windows 7 x64) i can't install anymore MSI files remotely through powershell...

Here is the error message :

"The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation."

Once i uninstalled the KB all is working fine.

Help needed ! I can't uninstall KB2918614 on all computers...

Workaround that is working for me:

Uninstall the application and reinstall it with the security update installed. (sourcehash file generated with security update)

Manually copy the sourcehash file to c:\windows\installer folder. As the sourcehash file is generated based on the application files, the sourcehash file generated on computer A can be used on computer B.“

The elevation prompt for admin credentials is coming up when the SecureHash for the product needs to be created
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-09T15:55:21+00:00

Got a replication with Lyve product installers provided to me. The replication was only for Windows 8 on a laptop with a roaming profile. I was not able to reproduce on Server 2012 or Server 2008 R2.

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate

REINSTALLMODE: vomus

OS: Windows 8 with latest updates including KB2918614

Profile: Roaming (only able to reproduce on a laptop)

MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type

MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10

MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}

MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded

MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=

MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0

MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0

MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs

MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3

MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640

MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035

MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0

MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin

[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp{a8554c44-e09c-479f-a8e5-685f5bf90487}.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'

[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079

[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.

[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve

[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'

[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.

[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.

[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None

[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been made more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
Was this answer helpful?

0 comments No comments