Resolved Issues with the Intel® Virtual RAID on CPU (Intel® VROC) 8.2 Release for Windows*
The following information lists the resolved issues with the Intel® VROC 8.2 release for Windows*. To learn about the latest updates of Intel® VROC for Windows*, refer to the Intel® Virtual RAID on CPU (Intel® VROC) Release Notes for Windows*.
| Issue ID | Description |
| 13010941224 | When creating a volume with 16-character name, the last character was being cut. |
| 14019194649 | Missing disk used to have the ID 0-255-0-0 after reboot. |
| 15012158141 | Enabling Intel® Volume Management Device (Intel® VMD) may increase boot time by 15 seconds without a hardware key plugged in. |
| 15012341358 | A wrong chipset number may be displayed incorrectly in the Intel® VROC Graphical User Interface (GUI) utility summary page. |
| 15012744995 | A page-fault exception may occur while calling EfiNvmExpressPassThru to send a EnableBlock SID command after hot-removing a NVMe* drive behind Intel® Volume Management Device (Intel® VMD). |
| 15012745887 | With the Micron* M.2 drive, there may be a disk error in which the BurnIn test:Test file could not be created. |
| 15012777627 | The event ID 4155 regarding CD/DVD ROM used to show invalid serial number of the device. |
| 15012986924 | The SATA RAID 1 volume rebuild speed was slower than expected which was fixed from very slow rebuild speeds from baseline, to what it should be at. |
| 15013305559 | Error events used to appear while activating the Out-of-Band (OOB) agent with Intel® Volume Management Device (Intel® VMD) disabled. |
| 15013356966 | After hot-unplugging of a RAID member, clearing metadata in another platform and re-plugging it back, disk usage is displayed incorrectly. |
| 15013389958 | Optimize hardware key detection, upgrade key is changed from premium to pass-thru during running reboot stress in the Windows* 10 22H2 operating system with BCB VMD. |
| 15013452250 | Disk usage is displayed as unknown after creating a RAID volume, deleting it, rebooting, setting disks to non-RAID, and checking usage in the Intel® VROC Graphical User Interface (GUI) utility. |
| 15013631093 | Confusing message used to appear after a RAID member was hot-unplugged and plug it back in. |
| 15014154518 | When heavy IO is added onto a degraded RAID 5 volume, there may be experienced errors relating to data mis-compare failures. |
| 18020894568 | While the disks are connected to the Platform Controller Hub (PCH), migrating the operating system volume to a RAID 5 volume with an additional drive from the same domain as member drives may end with error in the Intel® VROC Command-Line Interface (CLI) and Graphical User Interface (GUI) utilities. |
| 18020894601 | While connecting to disks under an Intel® Volume Management Device (Intel® VMD) domain, migrating the operating system volume to a RAID 5 volume with an additional drive from the same domain as member drives may end with error in the Intel® VROC Command-Line Interface (CLI) and Graphical User Interface (GUI) utilities. |
| 18021555907 | The increase size action could not be performed sometimes in the Intel® VROC Graphical User Interface (GUI) utility because of a refreshing issue. |
| 18022000029 | The VolumeDegraded and DriveRemoved events may not be detected after unplugging a volume member. |
| 18022848256 | The rebuild action may be very slow with some cache settings set incorrectly. |
| 18022969815 | The user may be unable to choose a strip size of 128 for RAID 10 volumes in the Pre-OS. |
| 18023073780 | Migrating a volume to another level may be impossible when the user changes the name of volume. |
| 18023113317 | When attempting to create a matrix RAID volume, the Intel® VROC 8.0 Graphical User Interface (GUI) utility may become unresponsive or fail. |
| 18023423304 | A system RAID 5 volume with RAID Write Hole (RWH) Journaling Drive (JD) could not be created when other operating system was present in the machine. |
| 18023561138 | An unexpected event log could be seen after a platform reboot during the volume rebuild action. |
| 18023576509 | No warning about RAID Write Hole (RWH) Journaling Drive (JD) not being supported for Linux* may appear during the RAID 5 volume creation in HII. |
| 18024043614 | Media errors could be counted incorrectly after initialization. |
| 18024488340 | The volume type could be changed from RAID 0 to RAID 5 with a x8 drive. |
| 18024577214 | Invalid RAID Write Hole (RWH) policy may return incorrect error for R0. |
| 18024634800 | A spanning warning string may be incorrect during creating a spanned RAID volume in EFI. |
| 18024662541 | The strip size of a volume could be changed during adding disk in one command. |
| 18024874787 | Registers used for saving AVX instruction states could get corrupted while using a RAID 5 volume. |
| 18025145965 | Under specific circumstances, the journaling drive may be in incorrect state. |
| 18025342659 | The eject disk button was unintentionally enabled in the Intel® VROC Graphical User Interface (GUI) utility, suggesting it is possible to perform an illegal action. |
| 18025418868 | The InitializeMethod value could be set incorrectly. |
| 18025554947 | Creating a volume may be impossible without stating optional parameters. |
| 18025555817 | The volume state may be incorrect in HII during initialization process. |
| 18025556051 | Under specific circumstances it was possible to fail a spanned RAID 5 volume while updating the Intel® VROC driver version. |
| 18025836360 | With a SATA RAID 5 volume, there may be an operating system message: System Hang 72, during the period when a system enters into S4 hibernate state. |
| 18025942408 | Once the user invoked the SetEvetReceiver command with value = disable, all events generated by Intel® VROC Out-of-Band (OOB) were supposed to be cleared in the event queue, which was not implemented correctly. |
| 18027972005 | The LED behavior between Linux*, Windows* and HII has been unified. It is now possible to turn off the LED manually in Windows*. |
| 18028910237 | Creating a volume with an invalid strip size value may be possible. |
| 18030599433 | The Secure Erase feature for NVMe* drives has been added. |
| 18030917271 | The volume name may not be shown fully and properly if it is equal to 16 characters. |
| 18031169423 | Creating a volume on a disk with data and non-existing OdataId may return incorrect error. |
| 18031491855 | The Smart App Control could block Intel® VROC driver actions. |
| Looking for more information about the Intel® VROC 8.2 release? |
| Check out the following resources: |
| Related topics |
| Intel® Virtual RAID on CPU (Intel® VROC) Release Notes for Windows* |
| Release Notes for Intel® Virtual RAID on CPU (Intel® VROC) |
| Resources for Intel® Virtual RAID on CPU (Intel® VROC) |