Skip to main content

On 14 Feb 2023, the following two MS updates for Windows Server have caused issues with Alliance and IIS.

Windows 2016   KB5022838

Windows 2019   KB5022840

Users reported seeing IIS internal error messages, blank screens, etc. after these were deployed.  This was reported impacting Astea Browser, Publisher website and Mobile Edge by our customers.

 

We found a solution to the issue with the Windows Updates pushed last night.  The fix is to:

  1. On the affected server go to C:\Windows\System32\inetsrv\Config
  2. Open applicationHost.config
  3. Search for .msu
  4. Find this:

        <system.webServer>

            <webSocket enabled="false" receiveBufferLimit="4194304" pingInterval="00:00:10" />

            <staticContent>

                <mimeMap fileExtension=".msp" mimeType="application/octet-stream" />

                <mimeMap fileExtension=".msu" mimeType="application/octet-stream" />

                <mimeMap fileExtension=".apk" mimeType="application/octet-stream" />

            </staticContent>

        </system.webServer>

  1. Remove <mimeMap fileExtension=".msu" mimeType="application/octet-stream" />
  2. Save file
  3. Problem resolved

 

Note, this has to be done after the update.

Hi Phil

Do you know if we can take off this line before the windows update ?

Thanks

Hi Christophe,

We were focused on resolving issues for the customers who have already encountered the problem as the updates already occurred.

After checking:

Has to be done after - the config file is updated by the update and is not rolled back after the update is removed.

 

thanks for the feedback

Also just reported from another customer seeing the same issues but are from a different Windows update also released on 14-Feb 2023:

We have a patch KB5022782 with one of the sub patches in it KB5022511.

When we install this patch the Astea web ,publisher and mobile is broken.

The same fix above has also resolved the issue for them.

 

FYI - we rolled back to an unupdated Windows version (from backup, as the update will not roll back), and disabled automatic Windows Updates. Updating Windows Malicious Software removal Tool (KB5022838) “broke” IIS in the same way - fix worked fine

Reply


Terms & ConditionsCookie settings