The current work around is just not use BIF_NEWDIALOGSTYLE flag.
This flag has been documented for 15+ years and MSDN says nothing about not using it when running on Hyper-V so this is a bug in Windows.
This impacts the installer made for hyper-v.
The current work around is just not use BIF_NEWDIALOGSTYLE flag.
This flag has been documented for 15+ years and MSDN says nothing about not using it when running on Hyper-V so this is a bug in Windows.
This impacts the installer made for hyper-v.