Describe the bug
The AfterPrep setting in registry seems to be applied after the VHD got dismounted. This means that the vDisk has still the AfterInst setting in registry. This causes the BIS-F framework to kickoff both the PREP and PERS phase as soon as the vDisk has started in read-only mode.
We're not using custom scripts, we're applying BIS-F settings by registry and not via GPO
If you check the PREP logfile on the reference VM you'll see that the VHD got dismounted before the state changes into AfterPrep, which explains the AfterInst state in the offline VHD registry.
Steps to reproduce
- Mount the sealed VHD on another Windows machine
- Load the offline HKLM\Software registry hive (mounted driveletter\Windows\System32\Config\SOFTWARE\
- Check the Registry setting in loaded hive\Login Consultants\BISF\LIC_BISF_PersState
Expected behavior
Setting should be AfterPrep instead of AfterInst in the offline sealed VHD.
Screenshots
Desktop, please complete the following information.
No response
Smartphone, please complete the following information.
No response
Additional context
No response
Describe the bug
The AfterPrep setting in registry seems to be applied after the VHD got dismounted. This means that the vDisk has still the AfterInst setting in registry. This causes the BIS-F framework to kickoff both the PREP and PERS phase as soon as the vDisk has started in read-only mode.
We're not using custom scripts, we're applying BIS-F settings by registry and not via GPO
If you check the PREP logfile on the reference VM you'll see that the VHD got dismounted before the state changes into AfterPrep, which explains the AfterInst state in the offline VHD registry.
Steps to reproduce
Expected behavior
Setting should be AfterPrep instead of AfterInst in the offline sealed VHD.
Screenshots
Desktop, please complete the following information.
No response
Smartphone, please complete the following information.
No response
Additional context
No response