I keep forgetting this and have to look it up the few times I need it… so I’m going to post it here:

  1. When setting NTFS permissions, select local machine (not the domain or whatever)
  2. Add “IIS AppPool\DefaultAppPool”
    (Don’t forget to change “DefaultAppPool” here to whatever you named your application pool)

That’s it ¯\_(ツ)_/¯

 

The application has failed to start because the side-by-side configuration is incorrect

Ugh, yeah one of those… alright let’s have a look…

So after (successfully) installing it, it does not want to start, so we have to do some tracing.

Eventlogs tells you only so much unfortunately so we look in the SxsTrace.exe  for help

This will open the SxSTrace.txt file which will have all the information about the error.

If that did not create any helpful information (but I hope it did) there are other steps that might help:

and let’s try DISM

Last resort options are a System Restore or updating .NET to the latest version.

 

 

 

 

 

You probably have heard or read about the current issues with chips and their vulnerability.

A fundamental design flaw in Intel’s processor chips has forced a significant redesign of the Linux and Windows kernels to defang the chip-level security bug.

CVE-2017-5754 (Meltdown) and CVE-2017-5715 (Spectre)  are two nasty exploits and you might want to check your systems if they are patched.

Luckily the Microsoft Security Response Center has released a PowerShell module named SpeculationControl which can be installed from the PowerShell Gallery.

Additionally maybe look at Mike’s post