Fleet stuck verifying `DevicePasswordEnabled` and `MaxInactivityTimeDeviceLock` config profile

[GrayW]

Fleet version: 4.81.0 | 4.81.1

Web browser and operating system: Windows 11 25H2 - Professional

---

💥  Actual behavior

When deploying a configuration profile for Windows to set DevicePasswordEnabled and MaxInactivityTimeDeviceLock, the profile remains stuck in a verifying state. Even after settings are applied as expected.

<Replace>
  <!-- Enable device password (0 = Enabled) -->
  <Item>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
    </Meta>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/Config/DeviceLock/DevicePasswordEnabled</LocURI>
    </Target>
    <Data>0</Data>
  </Item>

  <!-- Lock after 5 minutes of inactivity (value is in MINUTES) -->
  <Item>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
    </Meta>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/Config/DeviceLock/MaxInactivityTimeDeviceLock</LocURI>
    </Target>
    <Data>5</Data>
  </Item>
</Replace>

MDM PolicyManager: Set policy int, Policy: (DevicePasswordEnabled), Area: (DeviceLock), EnrollmentID requesting merge: (994C90D3-8B0E-48BE-BB1E-B386CB95682C), Current User: (Device), Int: (0x0), Enrollment Type: (0x0), Scope: (0x0).

MDM PolicyManager: Set policy int, Policy: (MaxInactivityTimeDeviceLock), Area: (DeviceLock), EnrollmentID requesting merge: (994C90D3-8B0E-48BE-BB1E-B386CB95682C), Current User: (Device), Int: (0x5), Enrollment Type: (0x0), Scope: (0x0).

🛠️ To fix

TODO

🧑‍💻  Steps to reproduce

These steps:

• Have been confirmed to consistently lead to reproduction in multiple Fleet instances.

1. Deploy included configuration profile to Windows host
2. Check Event Viewer to see that items are merged
3. Confirm that value has updated in registry
4. Profile remains in verifying state

🕯️ More info (optional)

N/A

[Sampfluger88]

Linked to Unthread ticket:

Conversation #12605

[MagnusHJensen]

Hi @GrayW Not sure what to do about these, but Windows verification (Verifying state) will go away, and we will solely rely on getting an OK from the device upon initial profile placement onto the device.

The story is in 4.83 and has been completed, so it's on track for the release date of 4.83:
#31921

[GrayW]

Thanks @MagnusHJensen, I've updated the customer and will watch #31921. Closing.

[fleet-release]

Stuck in verifying,
A glitch in the cloud city,
Fix brings clarity.

With each code tweak true,
Device lock settings renew,
Fleet's power in view.

[fleet-release]

Through Fleet's vast skies,
Locks devices, verifies -
Safety harmonized.