How to check if your Secure Boot certs are updated. (three methods)

hader · Dec 19, 2025

HeavyHemi said:
The only thing that I still don't have, that I have been told I do not need, is the Microsoft UEFI CA 2023 in the Current UEFI DB. I've run that script you suggested several times and I get an access error in the event viewer.

Access error? Make sure to run the commands as admin.
Don't have that Microsoft UEFI CA 2023 in the current EUFI DB? It should be there. That was the whole point.

If not? Run these commands, again Powershell as admin
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

After that check with regedit if the value of AvailableUpdates went back to 0x0
Querys;
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v UEFICA2023Status
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v WindowsUEFICA2023Capable

The response should be;
AvailableUpdates REG_DWORD 0x0
UEFICA2023Status REG_SZ Updated
WindowsUEFICA2023Capable REG_DWORD 0x2

hader · Dec 19, 2025

nikki605 said:
@hader The commands in your post didn't display.

Not sure what you mean. I can see everything I posted.
Again;
Commands are: (powershell as admin)

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x200 /f
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

Ah..... You mean; You are using the Light theme.... Chips. did not think about that......

nikki605 · Dec 19, 2025

hader said:
Not sure what you mean. I can see everything I posted.
Again;
Commands are: (powershell as admin)

Ah..... You mean; You are using the Light theme.... Chips. did not think about that......

Yes, light theme.

Now I can see the commands and will run them. I'll post the results.

Dirtyflash · Dec 19, 2025

pietcorus2 said:
Im on ASUS Z97-K , legacy-bios , no secure-boot enabled , latest bios-update from 05-02-2020.
Just checked ; no updates available , from the ASUS-site.

WHAT ?? , should I do , after reading the secure-boot forums .............?
(btw; this PC works very fine on latest Win11 , booting fast also......)

Do I really need " secure boot" and EUFI instead of legacy..............!!!?

Everyone has an opinion, I'll take the position that it's preferred to have secure boot enabled. If you don't have keys on your device to launch nuclear weapons and wipe out mankind, it shouldn't be much of an issue and you shouldn't worry too much.

pietcorus2 · Dec 19, 2025

Ok , so this "secure boot " is no problem for me anymore , coz I stay on legacy bios...........! :wink:

nikki605 · Dec 19, 2025

hader said:
Not sure what you mean. I can see everything I posted.
Again;
Commands are: (powershell as admin)

Ah..... You mean; You are using the Light theme.... Chips. did not think about that......

TADA!!! I'm down to 1 red X which you said is okay. Looks like I'm done on this machine.

hader · Dec 19, 2025

nikki605 said:
TADA!!! I'm down to 1 red X which you said is okay. Looks like I'm done on this machine.

View attachment 157437

Yes this the result what it should be. Done. Everything is updated en ready. Now wait until MS replace all their signed files by an update. They are pointing now to CA 2011, and through that update it will point towards CA 2023.

nikki605 · Dec 19, 2025

hader said:
Yes this the result what it should be. Done. Everything is updated en ready. Now wait until MS replace all their signed files by an update. They are pointing now to CA 2011, and through that update it will point towards CA 2023.

How is a novice, non-techie user ever going to deal with this. SMH

HeavyHemi · Dec 19, 2025

hader said:
Access error? Make sure to run the commands as admin.
Don't have that Microsoft UEFI CA 2023 in the current EUFI DB? It should be there. That was the whole point.

If not? Run these commands, again Powershell as admin
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

After that check with regedit if the value of AvailableUpdates went back to 0x0
Querys;
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v UEFICA2023Status
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v WindowsUEFICA2023Capable

The response should be;
AvailableUpdates REG_DWORD 0x0
UEFICA2023Status REG_SZ Updated
WindowsUEFICA2023Capable REG_DWORD 0x2

I'm sure you have not gone through my posting history to know that I have done these commands repeatedly over the last month or so.

I am aware that I need to run them with an elevated command prompt or elevated Powershell. I get the access errors as I stated regardless of the method used. I just ran them again and this is the result I get:

Here's the event viewer after I run the commands

starchase · Dec 19, 2025

I just ran the Check UEFI PK, KEK, DB and DBX.cmd (R-click and run as Administrator) and got this. Need to know about these warnings!
Note: all the "v" characters are green checks.

Code:

Checking for Administrator permission...
Running as administrator - continuing execution...

19 December 2025
Manufacturer: Hewlett-Packard
Model: HP Spectre x360 Convertible 13
BIOS: American Megatrends Inc., F.54, F.54, HPQOEM - 1072009
Windows version: 25H2 (Build 26200.7462)

Secure Boot status: Enabled

Current UEFI PK
v Mosby Generated PK [2025.12.17]

Default UEFI PK
WARNING: Failed to query UEFI variable PKDefault
                                                                                                                        
Current UEFI KEK                                                                                                        
v Microsoft Corporation KEK CA 2011 (revoked: False)                                                                    
v Microsoft Corporation KEK 2K CA 2023 (revoked: False)                                                                                                                                                                                         
Default UEFI KEK                                                                                                       
 WARNING: Failed to query UEFI variable 'KEKDefault' for cert 'Microsoft Corporation KEK CA 2011'                        
WARNING: Failed to query UEFI variable 'KEKDefault' for cert 'Microsoft Corporation KEK 2K CA 2023'                     
WARNING: Failed to query UEFI variable 'KEKDefault'        
                                                             
Current UEFI DB
v Microsoft Windows Production PCA 2011 (revoked: False)
v Microsoft Corporation UEFI CA 2011 (revoked: False)
v Windows UEFI CA 2023 (revoked: False)
v Microsoft UEFI CA 2023 (revoked: False)
v Microsoft Option ROM UEFI CA 2023 (revoked: False)
v MosbyKey [2025.12.17] (revoked: False)

Default UEFI DB
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Windows Production PCA 2011'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Corporation UEFI CA 2011'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Windows UEFI CA 2023'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft UEFI CA 2023'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Option ROM UEFI CA 2023'
WARNING: Failed to query UEFI variable 'DBDefault'

Current UEFI DBX
2025-10-14 (v1.6.0) : SUCCESS: 431 successes detected
Windows Bootmgr SVN : 7.0
Windows cdboot SVN  : 3.0
Windows wdsmgfw SVN : 3.0

Press any key to continue . . .

Here is the output of the Check_EFIBootFile.ps1 run:

Code:

PS C:\temp> powershell -nop -ep bypass -f Check_EFIBootFile.ps1
Secure Boot: ON
BitLocker on (C:) OFF

UEFI KEK Certs
--------------
    Microsoft Corporation KEK CA 2011
    Microsoft Corporation KEK 2K CA 2023

UEFI DB Certs
-------------
    Microsoft Corporation UEFI CA 2011
    Microsoft Windows Production PCA 2011
    Microsoft Option ROM UEFI CA 2023
    Microsoft UEFI CA 2023
    Windows UEFI CA 2023

UEFI DBX Certs
--------------

EFI Files
---------
    Disk 0: Boot Manager [Windows UEFI CA 2023] is ALLOWED.

    Registry: WindowsUEFICA2023Capable = 2
        [Windows UEFI CA 2023] is in UEFI DB, and Windows is starting from CA 2023 Boot Manager.

hader · Dec 19, 2025

nikki605 said:
How is a novice, non-techie user ever going to deal with this. SMH

You're not !!!!

Look. This issue came about because MS made a mistake during on off their update (Think 6899) TPM-WMI errors started to occur in the system logbooks of Windows. So they woke up the dogs. And oh yes they started to bark loud!!!

My personal opinion? If MS had done their job without producing errors. Nobody would to be wiser. MS would placed this whole issue and changes inside their updates before Jun 2026. But because we noticed this error; the ball started to roll. We have now solved it ourselves ahead of time to be frank.

Normal users. You can't expect from them to do this stuff. They have a PC, Windows, Browse, e-mail, game a bit and that's it.

hader · Dec 19, 2025

HeavyHemi said:
I'm sure you have not gone through my posting history to know that I have done these commands repeatedly over the last month or so. I am aware that I need to run them with an elevated command prompt or elevated Powershell. I get the access errors as I stated regardless of the method used. I just ran them again and this is the result I get: View attachment 157441

OK clear enough. You have to focus on those error codes. They are telling something. That is the main reason why the status is holding onto "InProgress". forever. You can wait of reboot a 1000 times it will not solve this problem. Looking at the error it's saying "not enough rights" Occurred when you try to initiate something without being a admin. Make sure that your system is OK using DISM /Restorehealth and SFC /scannow. There may be an issue here.

If I compare it with mine; UEFICAError and UEFICAErrorError are not there. UEFICA2023Status is Updated and WindowsEFICA2023Capable is 0x2.
In the part below it "DeviceAttributes" I see some info about my motherboard. Is inside SecureBoot, AvailiableUpdates stil 0x0?

Delete those keys; UEFICAError and UEFICAErrorError. They might be from an other attempt. They should not be there only in cases things went wrong.

Retry again now. There seems to be something wrong with that CA 2023 certificate. You can see it also in the eventviewer.

So let's correct that first with these commands (Powershell as admin)
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

Querys;
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v UEFICA2023Status
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v WindowsUEFICA2023Capable

The response should be;
AvailableUpdates REG_DWORD 0x0
UEFICA2023Status REG_SZ Updated
WindowsUEFICA2023Capable REG_DWORD 0x2

Are those UEFICAError and UEFICAErrorError back again? And is Status is again InProgress?
My BucketHash is filled with some kind of checksum value (SHA-256) (can be empty also) And the ConfidenceLevel is empty. Besides UEFICA2023Status and WindowsUEFICA2023Capable There should not be any keys normally in this tree-part.

HeavyHemi · Dec 19, 2025

hader said:
OK clear enough. You have to focus on those error codes. They are telling something. That is the main reason why the status is holding onto "InProgress". forever. You can wait of reboot a 1000 times it will not solve this problem. Looking at the error it's saying "not enough rights" Occurred when you try to initiate something without being a admin. Make sure that your system is OK using DISM /Restorehealth and SFC /scannow. There may be an issue here.

If I compare it with mine; UEFICAError and UEFICAErrorError are not there. UEFICA2023Status is Updated and WindowsEFICA2023Capable is 0x2.
In the part below it "DeviceAttributes" I see some info about my motherboard. Is inside SecureBoot, AvailiableUpdates stil 0x0?

Delete those keys; UEFICAError and UEFICAErrorError. They might be from an other attempt. They should not be there only in cases things went wrong.

Retry again now. There seems to be something wrong with that CA 2023 certificate. You can see it also in the eventviewer.

So let's correct that first with these commands (Powershell as admin)
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

Querys;
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot /v AvailableUpdates
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v UEFICA2023Status
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing /v WindowsUEFICA2023Capable

The response should be;
AvailableUpdates REG_DWORD 0x0
UEFICA2023Status REG_SZ Updated
WindowsUEFICA2023Capable REG_DWORD 0x2

Are those UEFICAError and UEFICAErrorError back again? And is Status is again InProgress?
My BucketHash is filled with some kind of checksum value (SHA-256) (can be empty also) And the ConfidenceLevel is empty. Besides UEFICA2023Status and WindowsUEFICA2023Capable There should not be any keys normally in this tree-part.

I realize you're trying to help, but asking me to run the exact same commands I've done repeatedly and using the same trouble shooting steps and expecting a different result does not seem helpful.

I've also been assured that I don't need this particular item for the system to run correctly.

starchase · Dec 19, 2025

starchase said:

I just ran the Check UEFI PK, KEK, DB and DBX.cmd (R-click and run as Administrator) and got this. Need to know about these warnings!
Note: all the "v" characters are green checks.

Code:

Checking for Administrator permission...
Running as administrator - continuing execution...

19 December 2025
Manufacturer: Hewlett-Packard
Model: HP Spectre x360 Convertible 13
BIOS: American Megatrends Inc., F.54, F.54, HPQOEM - 1072009
Windows version: 25H2 (Build 26200.7462)

Secure Boot status: Enabled

Current UEFI PK
v Mosby Generated PK [2025.12.17]

Default UEFI PK
WARNING: Failed to query UEFI variable PKDefault
                                                                                                                       
Current UEFI KEK                                                                                                       
v Microsoft Corporation KEK CA 2011 (revoked: False)                                                                   
v Microsoft Corporation KEK 2K CA 2023 (revoked: False)                                                                                                                                                                                        
Default UEFI KEK                                                                                                      
 WARNING: Failed to query UEFI variable 'KEKDefault' for cert 'Microsoft Corporation KEK CA 2011'                       
WARNING: Failed to query UEFI variable 'KEKDefault' for cert 'Microsoft Corporation KEK 2K CA 2023'                    
WARNING: Failed to query UEFI variable 'KEKDefault'       
                                                            
Current UEFI DB
v Microsoft Windows Production PCA 2011 (revoked: False)
v Microsoft Corporation UEFI CA 2011 (revoked: False)
v Windows UEFI CA 2023 (revoked: False)
v Microsoft UEFI CA 2023 (revoked: False)
v Microsoft Option ROM UEFI CA 2023 (revoked: False)
v MosbyKey [2025.12.17] (revoked: False)

Default UEFI DB
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Windows Production PCA 2011'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Corporation UEFI CA 2011'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Windows UEFI CA 2023'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft UEFI CA 2023'
WARNING: Failed to query UEFI variable 'dbDefault' for cert 'Microsoft Option ROM UEFI CA 2023'
WARNING: Failed to query UEFI variable 'DBDefault'

Current UEFI DBX
2025-10-14 (v1.6.0) : SUCCESS: 431 successes detected
Windows Bootmgr SVN : 7.0
Windows cdboot SVN  : 3.0
Windows wdsmgfw SVN : 3.0

Press any key to continue . . .

Here is the output of the Check_EFIBootFile.ps1 run:

Code:

PS C:\temp> powershell -nop -ep bypass -f Check_EFIBootFile.ps1
Secure Boot: ON
BitLocker on (C:) OFF

UEFI KEK Certs
--------------
    Microsoft Corporation KEK CA 2011
    Microsoft Corporation KEK 2K CA 2023

UEFI DB Certs
-------------
    Microsoft Corporation UEFI CA 2011
    Microsoft Windows Production PCA 2011
    Microsoft Option ROM UEFI CA 2023
    Microsoft UEFI CA 2023
    Windows UEFI CA 2023

UEFI DBX Certs
--------------

EFI Files
---------
    Disk 0: Boot Manager [Windows UEFI CA 2023] is ALLOWED.

    Registry: WindowsUEFICA2023Capable = 2
        [Windows UEFI CA 2023] is in UEFI DB, and Windows is starting from CA 2023 Boot Manager.

Since the lines showing "Current UEFI ..." locations are all green check marked, and the error codes are all in the so-called "Default UEFI" locations I'm going to assume that my machine is set up just fine and the error codes are really irrelevant for purposes of running the laptop.

garlin · Dec 20, 2025

Random trivia from script testing:

If you finished adding all the CA 2023 certs, UEFICA2023Status = Updated.
But if you go back and manually delete a cert (ie. Option ROM), UEFICA2023Status = NotStarted :think:

Code:

Secure Boot: OFF
BitLocker on (C:) OFF

UEFI KEK Certs
--------------
    Microsoft Corporation KEK CA 2011
    Microsoft Corporation KEK 2K CA 2023

UEFI DB Certs
-------------
    Microsoft Corporation UEFI CA 2011
    Microsoft Windows Production PCA 2011
    Microsoft UEFI CA 2023
    Windows UEFI CA 2023

UEFI DBX Certs
--------------
    Microsoft Windows Production PCA 2011
    Windows Boot Manager SVN 7.0

EFI Files
---------
    Disk 0: Windows Boot Manager [Windows UEFI CA 2023] is ALLOWED.

    Registry: WindowsUEFICA2023Capable = 2
        [Windows UEFI CA 2023] in UEFI DB, and Windows starting from CA 2023 Boot Manager.

PS C:\Users\GARLIN\Downloads> start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"
PS C:\Users\GARLIN\Downloads> reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing
    WindowsUEFICA2023Capable    REG_DWORD    0x2
    UEFICA2023Status    REG_SZ    NotStarted
    BucketHash    REG_SZ    4adea2baf22d03771e783bc274830e699f2c9e6ca97d2f8c720ff01139a08309
    ConfidenceLevel    REG_SZ

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing\DeviceAttributes
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing\UploadedForCurrentBootCycle

hader · Dec 20, 2025

HeavyHemi said:
I realize you're trying to help, but asking me to run the exact same commands I've done repeatedly and using the same trouble shooting steps and expecting a different result does not seem helpful. I've also been assured that I don't need this particular item for the system to run correctly.

OK. No need to complete quote me. If you say I am convinced that this will not help; there is then only one solution;
Apparently your administrator account seems to be damaged in such a way that the scheduled task script "Secure-Boot-Update" is giving rights errors. That (as I suggested) is an indication that your system is damaged. I would execute the In-Place-Installment procedure in order to refresh your whole Windows system. (all your data will be left alone)

"Not needed?"
You can also run further with the current system without any problems. Make sure you disable secure boot before June 2026. Because MS wil replaced all the Windows files with files signed with this new CA 2023 certificate. (Until then it will point to the be soon expiring CA 2011 certificate that gives you now no issues.) If you leave it as it is (secure boot=on) Windows will after the change refuse to boot. With secure boot disabled your system will run without any problems. But make sure that you have a good virusprogram that intercepts rootkit's that will try to inject or replace Windows files. With all the security risks that comes with it. (Ransomware for example) That is the whole point of MS; more secure. The bootloader will look during (startup) loading at drivers and files and inspects it certificate. If it's not right or the certificate has been expired: The bootload will not load them.

hader · Dec 20, 2025

starchase said:
Since the lines showing "Current UEFI ..." locations are all green check marked, and the error codes are all in the so-called "Default UEFI" locations I'm going to assume that my machine is set up just fine and the error codes are really irrelevant for purposes of running the laptop.

I agree. The current values are the one that are important. It is a bit strange that it can't get the default values.

It seems like that piece of memory has been wiped clean in the past. There is an option in the BIOS to wipe PK, KEK, DB, DBX values. Did you clear them in the past? Inside the BIOS: Under Boot-options, Secure Boot, Key management there is an option to "Install Default Secure Boot Keys" (besides "Clear Secure Boot keys") Do this and see it will now give you a normal result (without warnings). Other option is to reset all your values inside your BIOS (default values). If this does not help reflash your BIOS with your current one. Or you leave it as it is... Your choice.

All the values current and default ones are stored in a piece of NVRAM flashmemory on your motherboard. It is also the same location where your BIOS stores it's current BIOS values. During flashing a new BIOS version those default values of PK, KEK, DB and DBX will be filled also. It is possible that it will leave the current values alone. Because they were filled initial by the OEM (during manufacturing) with the default ones. (otherwise you have to repeat this whole CA2023 procedure again....)

hader · Dec 20, 2025

garlin said:
Random trivia from script testing:

If you finished adding all the CA 2023 certs, UEFICA2023Status = Updated.
But if you go back and manually delete a cert (ie. Option ROM), UEFICA2023Status = NotStarted

Not strange. It seems that that certificate must be there. If not then it does not meet the UEFICA2023 demands. You have to install it back again. Hope you have saved it somewhere. You can re-install it with certmgr.msc. The script "Secure-Boot-Update" (or some other check script) wants to see it. If not? It will say "Not updated, so NotStarted" And why bother? Secure boot is turned off..... It's only effective if secure boot = on.

Thierry 83200 · Dec 20, 2025

Good evening, is this situation satisfactory or should I do something else? Thank you for your help.
Sincerely,

HeavyHemi · Dec 20, 2025

I am not sure what happened here. I was in the BIOS and decided to save the secure boot keys. Exited out of the menu, rebooted and was greeted with this:

So, I go back in to the BIOS and notice that the authorized signatures was set to default. I tried to restore this from the save I had just made but apparently that didn't work.

So I had to disable secure boot to get back to the desktop. My secure boot now seems all jacked up.

How to check if your Secure Boot certs are updated. (three methods)

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Active member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

My Computers

My Computers

My Computers

My Computer

My Computers

My Computers

My Computers

My Computers

My Computer

My Computers

My Computers

My Computers

My Computer

My Computers

My Computer

My Computers

My Computers

My Computers

My Computer

My Computer