Share via

Encrypted files inaccessible

Anonymous
2025-01-04T10:34:21+00:00

Hi,

After new year, I have lost access to all my encrypted files. The files have existed since 10/8-2024, and was accessible until around 27/12-2024.

  • I only have one profile on the computer.
  • I have tried changing ownership of the files and folders, but it didn't work.

If i hit [Details] on Properties->Advance->[Details] (under Encrypt checkmark), i can see my account listed with a certificate thumbprint.

With powershell i can get the certificate using thumprint (Get-ChildItem -path 'Cert:\*34A50FB0897EB3D0E1B68EED94ACC8C38474B892' -Recurse | Format-List) and it is listed twice.

Subject      : CN=(account name)

Issuer       : CN=(account name)

Thumbprint   : 34A50FB0897EB3D0E1B68EED94ACC8C38474B892 

FriendlyName : 

NotBefore    : 10/1/2024 10:56:13 AM 

NotAfter     : 9/7/2124 10:56:13 AM 

Extensions   : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid} 

Subject      : CN=(account name)

Issuer       : CN=(account name)

Thumbprint   : 34A50FB0897EB3D0E1B68EED94ACC8C38474B892 

FriendlyName : 

NotBefore    : 10/1/2024 10:56:13 AM 

NotAfter     : 9/7/2124 10:56:13 AM 

Extensions   : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid}

(listed 2 times)

So the only thing to noticed, is that the CN= have a tailing whitespace in the name - if it matters?

I have tried the same on a different machine (old machine) where the encrypted files is (still) accessible, and it list around 8 entities. On those the CN= account name have no tailing whitespace.

What is next step to investigate?

***moved from Windows / Windows 10 / Accessibility***

Windows for business | Windows Client for IT Pros | Devices and deployment | Recovery key

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-01-07T08:25:30+00:00

    a follow up, and further investigations

    Seems I was wrong on the tailing whitespace in the CN= account name, a second check didn't have it(?)

    But i have created some new encrypted files, and they have a different certificate thumbprint:

    Subject      : CN=(account name) 
    
    Issuer       : CN=(account name) 
    
    Thumbprint   : C5270F3FAAAB6E6366E144AA5D1D86056D37999E 
    
    FriendlyName : 
    
    NotBefore    : 12/12/2024 10:12:07 AM 
    
    NotAfter     : 11/18/2124 10:12:07 AM 
    
    Extensions   : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid}
    

    (listed 6 times).

    I can access the new encrypted files.

    If i try press the [Back up keys] under the file, that is not accessible, i get following message box.

    So it is seems the problem is related to the certificate.

    Was this answer helpful?

    0 comments No comments