RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When creating a partition using diskpart in Windows pe 6.1.7600 with the drivers from the 1.65 ISO integrated into the image using DISM diskpart always creates an NTFS filesystem that has errors. You must manually chkdsk /f the partition before Windows will install on the new partition. 

Version-Release number of selected component (if applicable):

0.1-65

How reproducible:

1. Integrate the Win7\AMD64 drivers from virtio-win-0.1-65.iso into a Windows PE image using DISM
2. Boot a VM from the WinPE ISO or via PXE
3. use diskpart to create a partition
4. Run chkdsk on the new partition (it will have FS errors)
5. Run chkdsk /f on the new partition (it will fix the FS errors)

Actual results:

Using the 0.1-65 drivers and creating a partition from Windows PE causes a partition with errors to be created.

Expected results:

A partition with no errors should be created.

Additional info:

*** This bug has been marked as a duplicate of bug 966861 ***