{"id":36157,"date":"2024-10-12T00:01:05","date_gmt":"2024-10-11T22:01:05","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=36157"},"modified":"2024-10-19T00:58:27","modified_gmt":"2024-10-18T22:58:27","slug":"windows-11-24h2-serious-issues-after-upgrade","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/10\/12\/windows-11-24h2-serious-issues-after-upgrade\/","title":{"rendered":"Windows 11 24H2: Serious issues after upgrade"},"content":{"rendered":"

\"Windows\"[German<\/a>]After upgrading to Windows 11 24H2, some users experience very unpleasant surprises. In addition to bugs already documented by Microsoft, new errors are occurring. The sfc \/scannow command displays corrupt files. Or 8.63 GB of data that cannot be deleted by disk cleanup accumulates in the update cache. Let me summarize some of the findings I have come across.<\/p>\n

<\/p>\n

\"\"In the blog post Windows 11 24H2: Numerous show-stoppers and known bugs<\/a>, I pointed out some bugs and show stoppers that Microsoft had already published hours before the release of Windows 11 24H2. This also includes the fact that the upgrade is blocked on some PCs due to BSOD because of outdated Intel drivers.<\/p>\n

Microsoft has suspended the upgrade to Windows 11 24H2 on certain Intel PCs. The cause is older Intel SST drivers, which lead to BlueScreens (BSODs) on the machines. The colleagues from Bleeping Computer have also published some information about this in this article<\/a>.<\/p>\n

Faulty files with sfc<\/h2>\n

Robert has reported in this German comment<\/a> to my German article\u00a0Windows 11 24H verf\u00fcgbar (1. Oktober 2024)<\/a>, that the command sfc \/verifyonly<\/em> leads to messages about corrupt files. In the course of the discussion it is stated that the broken files belong to Webview2.<\/p>\n

\"Windows<\/a><\/p>\n

Windows Latest has since addressed the issue in the above tweet and linked to this article<\/a> with further details. I got mixed feedback from readers, the the Windows 11 24H2 preview update KB5044384 f has (not) fixed the bug.<\/p>\n

Mouse pointer disappears<\/h2>\n

Another bug that can annoy users of Windows 11 24H2 has been picked up by Windows Latest in the article A Windows 11 24H2 bug is so odd that it causes the mouse pointer\/cursor to disappear<\/a>. The current operating system version has the peculiarity that the cursor\/mouse pointer disappears in text input fields.<\/p>\n

After upgrading to the Windows 11 24H2 update, article author Mayank Parmar noticed that Google Chrome, Microsoft Edge, Slack, Spotify and any app based on the Chromium engine is unable to recognize the mouse pointer when a text field is selected. However, Mayank Parmar has found a workaround: You have to select the default cursor for the mouse so that it remains visible.<\/p>\n

8.3 GB of undeletable data in the update cache<\/h2>\n

After installing Windows 11 24H2, a bug creates an 8.63 GB Windows update cache that cannot be deleted with Disk Cleanup or the storage settings.<\/p>\n

\"Windows<\/a><\/p>\n

Normally, it should be possible to delete such files using Disk Cleanup, as they are no longer needed. Mayank Parmar was probably one of the first to report the problem in this article<\/a> on Windows Latest.<\/p>\n

These\u00a0 non-deletable updates are related to the new feature \"staged checkpoint\" and \"checkpoint cumulative updates\". These \"staged checkpoint\" updates cannot be deleted because the \"checkpoint cumulative\" updates are based on the previous \"staged checkpoint\".\u00a0The problem is now known at Microsoft and will be fixed with one of the upcoming updates (I guess, MS will hide the part in Windows Update cache).<\/p>\n

DirectAccess broken<\/h2>\n

DirectAccess has enabled clients to connect to corporate networks without installing a VPN since Windows 7 and Windows Server 2008 R2. In June 2024, Microsoft discontinued DirectAccess and wrote that this feature would be replaced by Always On VPN (see my article Windows: DirectAccess discontinued; Always On VPN recommended<\/a>).<\/p>\n

In the comment here<\/a>, a reader already pointed out that DirectAccess would no longer work after the feature upgrade to Windows 11 24H2. The reader wrote \"If someone uses 802.1x EAP-TLS for network authentication, it can happen that network adapters lose the configuration and authentication is no longer possible.\"\u00a0At neowin.net the topic has been taken up in this article<\/a>. It is unclear to me whether Microsoft will deliver a fix.<\/p>\n

Similar article:<\/strong>
\nWindows 11 24H released (Oktober 1, 2024)<\/a>
\nWindows 11 24H2: Numerous show-stoppers and known bugs<\/a>
\nWindows 11 24H2: Serious issues after upgrade<\/a>
\nWindows: DirectAccess discontinued; Always On VPN recommended<\/a>
\nAttention: Windows 11 24H2 changed default settings for standby<\/a>
\nWindows 11 24H2: Administrative templates (.admx)<\/a>
\nWindows 11 24H2: Activation lost?<\/a>
\nWindows 11 24H2: SMB read\/write transfer rate extremely slow?<\/a>
\nWindows 11 24H2: Issues with VPN connections, Direct Access \u2026<\/a>
\nWindows 11 24H2: Recall can't be uninstalled; and \"poor mans recall\" found<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]After upgrading to Windows 11 24H2, some users experience very unpleasant surprises. In addition to bugs already documented by Microsoft, new errors are occurring. The sfc \/scannow command displays corrupt files. Or 8.63 GB of data that cannot be deleted … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[47,2860],"class_list":["post-36157","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-issue","tag-windows-11-24h2"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=36157"}],"version-history":[{"count":2,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36157\/revisions"}],"predecessor-version":[{"id":36198,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36157\/revisions\/36198"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=36157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=36157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=36157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}