Hi,
I made more tests on a fully updated Windows. The migration issue with dpapimig still exists.
I notices some points:
- The issue seems to be related to lsass. (according to procmon)
- The migration works when the 2 computers SID are the same. After a sysprep, a working Windows server is not able to do migration. When I restore the computer SID using sidchg (https://www.stratesave.com/html/sidchg.html), The migration works again.
The tool dpapimig and the API CryptUpdateProtectedState are still supported ?
Best regards,
David.