ECC memory requirementsfor Azure Stack HCI, version 23H2

Has there recently been an ECC memory requirement implemented for Azure Stack HCI 23H2? There is nothing on the Server and storage requirements page that indicates that ECC memory is required (see here). However, when attempting to deploy a 2-node cluster in my home lab today (using two Minisforum MS-01 workstations), I get the following error during the validation phase:

Type 'ValidateHardware' of Role 'EnvironmentValidator' raised an exception: { "ExceptionType": "json", "ErrorMessage": { "Message": "Hardware requirements not met. Review output and remediate.", "Results": [ { "Name": "AzStackHci_Hardware_Test_PhysicalMemory_Instance_Property_ECC", "DisplayName": "Test PhysicalMemory Property ECC AP-AZHCI01", "Tags": { }, "Title": "Test PhysicalMemory Property ECC", "Status": 1, "Severity": 2, "Description": "Checking PhysicalMemory for property ECC has desired value", "Remediation": "https://aka.ms/hci-envch", "TargetResourceID": "Machine: AP-AZHCI01, Class: PhysicalMemory, Instance: Controller0-ChannelA-DIMM0, Tag: Physical Memory 0", "TargetResourceName": "Machine: AP-AZHCI01, Class: PhysicalMemory, Instance: Controller0-ChannelA-DIMM0, Tag: Physical Memory 0", "TargetResourceType": "PhysicalMemory", "Timestamp": "\/Date(1731779752874)\/", "AdditionalData": { "Detail": "PhysicalMemory property \u0027ECC\u0027 value \u0027False\u0027. Expected \u0027True\u0027", "Status": "FAILURE", "TimeStamp": "11/16/2024 17:55:52", "Resource": "False", "Source": "PhysicalMemory: ECC" }, "HealthCheckSource": "Deployment\\Medium\\Hardware\\4b24f153" }, { "Name": "AzStackHci_Hardware_Test_PhysicalMemory_Instance_Property_ECC", "DisplayName": "Test PhysicalMemory Property ECC AP-AZHCI01", "Tags": { }, "Title": "Test PhysicalMemory Property ECC", "Status": 1, "Severity": 2, "Description": "Checking PhysicalMemory for property ECC has desired value", "Remediation": "https://aka.ms/hci-envch", "TargetResourceID": "Machine: AP-AZHCI01, Class: PhysicalMemory, Instance: Controller1-ChannelA-DIMM0, Tag: Physical Memory 1", "TargetResourceName": "Machine: AP-AZHCI01, Class: PhysicalMemory, Instance: Controller1-ChannelA-DIMM0, Tag: Physical Memory 1", "TargetResourceType": "PhysicalMemory", "Timestamp": "\/Date(1731779752889)\/", "AdditionalData": { "Detail": "PhysicalMemory property \u0027ECC\u0027 value \u0027False\u0027. Expected \u0027True\u0027", "Status": "FAILURE", "TimeStamp": "11/16/2024 17:55:52", "Resource": "False", "Source": "PhysicalMemory: ECC" }, "HealthCheckSource": "Deployment\\Medium\\Hardware\\4b24f153" }, { "Name": "AzStackHci_Hardware_Test_PhysicalMemory_Instance_Property_ECC", "DisplayName": "Test PhysicalMemory Property ECC AP-AZHCI02", "Tags": { }, "Title": "Test PhysicalMemory Property ECC", "Status": 1, "Severity": 2, "Description": "Checking PhysicalMemory for property ECC has desired value", "Remediation": "https://aka.ms/hci-envch", "TargetResourceID": "Machine: AP-AZHCI02, Class: PhysicalMemory, Instance: Controller0-ChannelA-DIMM0, Tag: Physical Memory 0", "TargetResourceName": "Machine: AP-AZHCI02, Class: PhysicalMemory, Instance: Controller0-ChannelA-DIMM0, Tag: Physical Memory 0", "TargetResourceType": "PhysicalMemory", "Timestamp": "\/Date(1731779753046)\/", "AdditionalData": { "Detail": "PhysicalMemory property \u0027ECC\u0027 value \u0027False\u0027. Expected \u0027True\u0027", "Status": "FAILURE", "TimeStamp": "11/16/2024 17:55:53", "Resource": "False", "Source": "PhysicalMemory: ECC" }, "HealthCheckSource": "Deployment\\Medium\\Hardware\\4b24f153" }, { "Name": "AzStackHci_Hardware_Test_PhysicalMemory_Instance_Property_ECC", "DisplayName": "Test PhysicalMemory Property ECC AP-AZHCI02", "Tags": { }, "Title": "Test PhysicalMemory Property ECC", "Status": 1, "Severity": 2, "Description": "Checking PhysicalMemory for property ECC has desired value", "Remediation": "https://aka.ms/hci-envch", "TargetResourceID": "Machine: AP-AZHCI02, Class: PhysicalMemory, Instance: Controller1-ChannelA-DIMM0, Tag: Physical Memory 1", "TargetResourceName": "Machine: AP-AZHCI02, Class: PhysicalMemory, Instance: Controller1-ChannelA-DIMM0, Tag: Physical Memory 1", "TargetResourceType": "PhysicalMemory", "Timestamp": "\/Date(1731779753077)\/", "AdditionalData": { "Detail": "PhysicalMemory property \u0027ECC\u0027 value \u0027False\u0027. Expected \u0027True\u0027", "Status": "FAILURE", "TimeStamp": "11/16/2024 17:55:53", "Resource": "False", "Source": "PhysicalMemory: ECC" }, "HealthCheckSource": "Deployment\\Medium\\Hardware\\4b24f153" } ] }, "ExceptionStackTrace": "at ParseResult, C:\\NugetStore\\AzStackHci.EnvironmentChecker.Deploy.1.2100.2845.573\\content\\Classes\\EnvironmentValidator\\EnvironmentValidator.psm1: line 1166 at Test-AzStackHciHardware, C:\\Program Files\\WindowsPowerShell\\Modules\\AzStackHci.EnvironmentChecker\\AzStackHciHardware\\AzStackHciHardware.psm1: line 110 at \u003cScriptBlock\u003e, \u003cNo file\u003e: line 1 at RunSingleValidator, C:\\NugetStore\\AzStackHci.EnvironmentChecker.Deploy.1.2100.2845.573\\content\\Classes\\EnvironmentValidator\\EnvironmentValidator.psm1: line 706 at ValidateHardware, C:\\NugetStore\\AzStackHci.EnvironmentChecker.Deploy.1.2100.2845.573\\content\\Classes\\EnvironmentValidator\\EnvironmentValidator.psm1: line 386 at \u003cScriptBlock\u003e, C:\\CloudDeployment\\ECEngine\\InvokeInterfaceInternal.psm1: line 139 at Invoke-EceInterfaceInternal, C:\\CloudDeployment\\ECEngine\\InvokeInterfaceInternal.psm1: line 134" } at RunSingleValidator, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.1.2100.2845.573\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 722 at ValidateHardware, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.1.2100.2845.573\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 386 at <ScriptBlock>, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 139 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 134

It appears others have successfully deployed Azure Stack HCI using this same hardware as recently as May 2024 (seemingly without ECC memory--I don't believe this chipset even supports ECC). I'd appreciate if anyone has any additional information on this requirement (or a way to bypass it).