Adept PC Repair
Active Member
- Reaction score
- 184
- Location
- Cardiff
I had a desperate customer yesterday who runs the local shop, needed to pay his staff their wages.
The payroll software updated and as such also required a .net runtime update which wouldn't install. The system was Windows 8 but I believe this solution applies to all operating systems.
Symptoms were:
Dism wouldn't recognise the clean-up image switch.
Turn Windows features on / off was blank in programs and features.
.net installer complaining of missing Windows module installer (not to be confused with Windows installer service).
Sfc/scannow would complain of a repair pending even though there was no pending.xml and the registry key wasn't present.
I came so close to a nuke and pave on this one, but here lies the solution.
Go to c:\windows\servicing and check if trustedinstaller.exe is present. If it isn't (which was the case for me) then you can get a copy of it from c:\windows\winsxs
You then need to take control of the servicing folder and copy the trustedinstaller.exe file you found in the winsxs folder to it.
Restart Windows, remember not to do this on an external computer if fast start-up is enabled if you choose to, as the file won't be there when you transfer the hdd to the original computer.
Sit back, install .net or whichever Windows feature you require. I was quite happy with this find and had to share.
The payroll software updated and as such also required a .net runtime update which wouldn't install. The system was Windows 8 but I believe this solution applies to all operating systems.
Symptoms were:
Dism wouldn't recognise the clean-up image switch.
Turn Windows features on / off was blank in programs and features.
.net installer complaining of missing Windows module installer (not to be confused with Windows installer service).
Sfc/scannow would complain of a repair pending even though there was no pending.xml and the registry key wasn't present.
I came so close to a nuke and pave on this one, but here lies the solution.
Go to c:\windows\servicing and check if trustedinstaller.exe is present. If it isn't (which was the case for me) then you can get a copy of it from c:\windows\winsxs
You then need to take control of the servicing folder and copy the trustedinstaller.exe file you found in the winsxs folder to it.
Restart Windows, remember not to do this on an external computer if fast start-up is enabled if you choose to, as the file won't be there when you transfer the hdd to the original computer.
Sit back, install .net or whichever Windows feature you require. I was quite happy with this find and had to share.
