{"id":632,"date":"2020-01-23T11:34:20","date_gmt":"2020-01-23T16:34:20","guid":{"rendered":"http:\/\/itblog.ldlnet.net\/?p=632"},"modified":"2020-01-23T11:34:20","modified_gmt":"2020-01-23T16:34:20","slug":"exchange-2019-setup-prerequisite-check-fails-for-net-4-8-framework-in-cu4-on-windows-builds-1909-and-1903","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2020\/01\/23\/exchange-2019-setup-prerequisite-check-fails-for-net-4-8-framework-in-cu4-on-windows-builds-1909-and-1903\/","title":{"rendered":"Exchange 2019 Setup Prerequisite Check fails for .NET 4.8 Framework in CU4 on Windows builds 1909 and 1903"},"content":{"rendered":"\n<h4 class=\"wp-block-heading\">Symptoms<\/h4>\n\n\n\n<p>When you\ndeploy or upgrade to Microsoft Exchange 2019 Cumulative Update 4 (CU4) on\nMicrosoft Windows Server 2019 or Windows 10 (Management Tools only) builds\n1909&nbsp;or 1903, the system prerequisites check fails, and you receive the\nfollowing error message:<\/p>\n\n\n\n<p class=\"has-text-color has-small-font-size has-medium-pink-color\"><strong><em>&#8220;This computer requires .NET Framework 4.8 (<a href=\"https:\/\/nam06.safelinks.protection.outlook.com\/?url=https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4503548&amp;data=02%7C01%7Cv-lalin%40microsoft.com%7Ce56c485a2d534c2988c508d79f95214e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637153335168852972&amp;sdata=Zc1QjT2b6GKGNZMN1e2UhJKoWH%2BUI59PBebopo44MvM%3D&amp;reserved=0\">https:\/\/support.microsoft.com\/kb\/4503548<\/a>).\u201d<\/em><\/strong><\/p>\n\n\n\n<p>By default, Windows builds 1909 and 1903 already have .NET Framework 4.8 installed. When you try to reinstall the software, the installation fails.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Cause<\/h4>\n\n\n\n<p>This\nproblem is caused by a prerequisite check that was introduced in Cumulative\nUpdate 4. This process checks incorrectly for .NET Framework 4.8. Because the\nprerequisite check doesn&#8217;t recognize that .NET Framework 4.8 is already\ninstalled.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Status<\/strong><\/h4>\n\n\n\n<p>Microsoft is researching this problem and will post more\ninformation in this article when it becomes available.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Workaround<\/h4>\n\n\n\n<p><strong>Important<\/strong><\/p>\n\n\n\n<p>Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Start \u201cregedit.exe\u201d as an administrator.<\/li><li>Locate the following registry subkey:<\/li><\/ul>\n\n\n\n<p class=\"has-text-color has-small-font-size has-purple-color\">HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\NET Framework\nSetup\\NDP\\v4\\Full<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Right-click the subkey, and select Permissions from the shortcut menu.<\/li><li>Select Advanced.<\/li><li>In the Advanced Security Settings window, locate the Owner attribute at the top of the window.<\/li><li>Select Change next to the listed owner.<\/li><li>In the Enter the object name to select field, enter the name of the local administrator group. For example, enter &lt;computername>\\Administrator.      Then, select OK.<\/li><li>In the Advanced Security Settings window, select the local administrator group that you changed ownership to, and then select Edit.<\/li><li>Change the basic permissions to Full Control.<\/li><li>Select OK three times to save the changes and return to the main Registry Editor window.<\/li><li>Locate the following key in the path:<\/li><\/ul>\n\n\n\n<p>Name: Release<br>Type: REG_DWORD<br>Data: 528040 (decimal)<br><em>Change the Data value to 528049 (decimal)<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Rerun the Exchange system prerequisites check, and deploy or update Exchange Server 2019.<\/li><li>Start Registry Editor, locate the subkey that&#8217;s mentioned in step 2, repeat the necessary steps to locate the Release key, and then revert the Data value to 528040 (decimal). <\/li><\/ul>\n\n\n\n<p>This should allow everything to run correctly after the installation.<\/p>\n\n\n\n<h2 class=\"has-text-align-center wp-block-heading\"><strong>POSITIVE DAY TO YOU! <\/strong><br><strong>FINE = Focused Intent Not Emotionalizing<\/strong><\/h2>\n\n\n\n<p><strong><em>REFERENCES<\/em><\/strong><br><a href=\"https:\/\/support.microsoft.com\/en-ph\/help\/4538303\/exchange-2019-setup-prerequisite-check-fails-for-net-4-8-framework\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"Exchange CU4 Prerequisite Check Fails for .NET 4.8 for Windows Server builds 1909 and 1903 (opens in a new tab)\">Exchange CU4 Prerequisite Check Fails for .NET 4.8 for Windows Server builds 1909 and 1903<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Symptoms When you deploy or upgrade to Microsoft Exchange 2019 Cumulative Update 4 (CU4) on Microsoft Windows Server 2019 or Windows 10<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/itblog.ldlnet.net\/index.php\/2020\/01\/23\/exchange-2019-setup-prerequisite-check-fails-for-net-4-8-framework-in-cu4-on-windows-builds-1909-and-1903\/\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":161,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,2],"tags":[9,151,221],"class_list":["post-632","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-exchange","category-general","tag-exchange","tag-exchange-2019","tag-installation","odd"],"_links":{"self":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/comments?post=632"}],"version-history":[{"count":3,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/632\/revisions"}],"predecessor-version":[{"id":635,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/632\/revisions\/635"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media\/161"}],"wp:attachment":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media?parent=632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/categories?post=632"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/tags?post=632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}