![]() ![]() Important: Later versions refer to just the last part of the version number. This issue is resolved by updating the Intel® Smart Sound Technology drivers to a version 10. Workaround: To mitigate the safeguard, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. If your organization is using Update Compliance, the safeguard IDs are: To safeguard your upgrade experience, we have applied a compatibility hold on devices with affected Intel SST drivers from being offered Windows 11, version 23H2, Windows 11, version 22H2, or Windows 11, version 21H2 on devices with Windows 10. Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10. The affected driver will be named Intel® Smart Sound Technology (Intel® SST) Audio Controller under System Devices in Device Manager and have the file name IntcAudioBus.sys and a file version of 10. Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11. Server: Windows Server 2022 Windows Server, version 20H2 Windows Server, version 1809 Windows Server 2019 Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 SP1 Windows Server 2008 SP2Ĭompatibility issues with Intel Smart Sound Technology drivers and Windows 11.Client: Windows 11, version 23H2 Windows 11, version 22H2 Windows 10, version 22H2 Windows 11, version 21H2 Windows 10, version 21H2 Windows 10, version 20H2 Windows 10, version 1809 Windows 10 Enterprise LTSC 2019 Windows 10 Enterprise LTSC 2016 Windows 10, version 1607 Windows 10 Enterprise 2015 LTSB. ![]() Resolution: This issue was resolved in updates released Octo( KB5031455) and later. ![]() Please view the settings and documentation for your applications. Some applications might not allow this manual change. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Manually changing currency might also be an option in some applications. Change the currency symbol from " KN" to Euro, " €"Īdditional information can be seen here: Currency formatting - Globalization | Microsoft Learn.In this same window, click the " Additional settings" button.In the Region settings, choose one of the 2 locales for Croatia:.On your keyboard, press and hold the Windows key, then press the letter R.Open " Control Panel" from the start menu and select " Change date, time, or number formats" under " Clock and Region".This can be done in one of the following ways: This can be accomplished via the Windows Control Panel. Workaround: Changing the currency in Windows can help. Windows Locale data for Croatia will be updated for this change in the short term. This can affect applications which retrieve the device's currency for purchases or other transactions.Įarlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. The correct default currency might not display or be used in Windows devices which have locale set to Croatia. Client: Windows 11, version 23H2 Windows 11, version 22H2 Windows 10, version 22H2 Windows 11, version 21H2 Windows 10, version 21H2 Windows 10 Enterprise LTSC 2019ĭevices with locale set to Croatia might not utilize the expected currency.Next steps: We are working on a resolution and will provide an update in an upcoming release. Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues. Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. BitLocker might incorrectly receive a 65000 error in MDMs ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |