Hi All,
Just a quick PSA about Windows11 upgrading to 24H2. I filed (and closed) a bug on this matter just to document the issue and the solution. I'm going to copy/paste the 'additional details from that issue here. I just wanted to try to let as many people know as possible in case this strange situation affects anyone else. This is not a ZDEW issue per-se. I filed a separate issue to move away from using APPDATA to try to prevent this issue in the future.
I expect this issue affects very few installations of ZDEW. However, if you had this issue, please let me/the community know by posting here? It will help us prioritize the possible move from APPDATA to PROGRAMDATA.
The Fix
- STOP the ZDEW
- copy the entire contents of
C:\Windows.old\WINDOWS\System32\config\systemprofile\AppData\Roaming\NetFoundrytoC:\Windows\WINDOWS\System32\config\systemprofile\AppData\Roaming\NetFoundry - start the ZDEW and your identities will return.
PSA follows
Windows 11 version 24H2 has not been installing on my system for months. Numerous sites have been indicating that Microsoft was aware of it and was working to fix it. For example: Microsoft confirms Windows 11 24H2 installation issues, newer updates fail for some PCs
Some sites have been reporting the only method to fix this issue is to reinstall the Windows OS. This appears to be the route Microsoft has taken. If Windows had a hard time upgrading to 24H2, there seems to be a chance that it will effectively "reinstall Windows" silently when updating. This should leave behind a folder at %SYSTEMDRIVE% named windows.old. For example, on my local machine, I had a c:\Windows.old created during this process:
