F5F Stay Refreshed Hardware Desktop New version reported by ftpm/psp indicates corruption or structural changes

New version reported by ftpm/psp indicates corruption or structural changes

New version reported by ftpm/psp indicates corruption or structural changes

F
Fireking124
Senior Member
576
10-09-2018, 07:37 PM
#1
You just completed a fresh installation and everything inside the case appears functional. However, when you power on the system, you encounter an error screen. I’m unsure what to do next. I’m using all new components except a few prebuilt fans. I haven’t replaced any storage, memory, motherboard or CPU—just the whole setup. The recovery key is unclear to me, and I’ve never used BitLocker before. Technically, my Ryzen 5 2600 is still present, but it might not fit the new motherboard, so that could be an issue. Windows 10 hasn’t been installed yet. I did connect the OS flash drive during startup, but if it doesn’t automatically attempt to install Windows, that should be fine. Could you share any additional details to help resolve this? Thank you!
F
Fireking124
10-09-2018, 07:37 PM #1

You just completed a fresh installation and everything inside the case appears functional. However, when you power on the system, you encounter an error screen. I’m unsure what to do next. I’m using all new components except a few prebuilt fans. I haven’t replaced any storage, memory, motherboard or CPU—just the whole setup. The recovery key is unclear to me, and I’ve never used BitLocker before. Technically, my Ryzen 5 2600 is still present, but it might not fit the new motherboard, so that could be an issue. Windows 10 hasn’t been installed yet. I did connect the OS flash drive during startup, but if it doesn’t automatically attempt to install Windows, that should be fine. Could you share any additional details to help resolve this? Thank you!

C
Charliemc909
Posting Freak
898
10-11-2018, 05:50 AM
#2
You pressed Y immediately. Any drive or motherboard you're using should still have a boot manager installed, especially after swapping components. I encountered this issue multiple times when changing CPUs or combining CPU and motherboard while keeping the same operating system, even with BitLocker active.
C
Charliemc909
10-11-2018, 05:50 AM #2

You pressed Y immediately. Any drive or motherboard you're using should still have a boot manager installed, especially after swapping components. I encountered this issue multiple times when changing CPUs or combining CPU and motherboard while keeping the same operating system, even with BitLocker active.

D
DURELL
Junior Member
27
10-12-2018, 11:46 PM
#3
If you press Y but it doesn’t work, you can reset the system and start fresh. It’s straightforward to turn it off and reboot, erasing any mistakes. This avoids unnecessary complications later.
D
DURELL
10-12-2018, 11:46 PM #3

If you press Y but it doesn’t work, you can reset the system and start fresh. It’s straightforward to turn it off and reboot, erasing any mistakes. This avoids unnecessary complications later.

D
228
10-13-2018, 01:39 AM
#4
It seems the approach of resetting the fTPM on a fresh build isn’t necessarily the issue. The bitlocker key you’re using shouldn’t be at risk here. Even if BitLocker is active and you encounter this warning, simply logging into your MS account and entering the key works. This error shouldn’t appear on a brand-new setup with a new motherboard and storage drive, suggesting either cached data or a boot manager conflict. Clearing the fTPM appears to be the most reliable solution. If everything is brand new—drives included—the concern leans toward a hidden component or firmware quirk on the board. Unless there’s an unexpected factor I haven’t noticed, it’s probably safe to proceed with the reset.
D
Danieltowersxd
10-13-2018, 01:39 AM #4

It seems the approach of resetting the fTPM on a fresh build isn’t necessarily the issue. The bitlocker key you’re using shouldn’t be at risk here. Even if BitLocker is active and you encounter this warning, simply logging into your MS account and entering the key works. This error shouldn’t appear on a brand-new setup with a new motherboard and storage drive, suggesting either cached data or a boot manager conflict. Clearing the fTPM appears to be the most reliable solution. If everything is brand new—drives included—the concern leans toward a hidden component or firmware quirk on the board. Unless there’s an unexpected factor I haven’t noticed, it’s probably safe to proceed with the reset.

P
pinkSparkle17
Member
192
10-16-2018, 08:45 AM
#5
Yes, hitting Y suggests a positive outcome.
P
pinkSparkle17
10-16-2018, 08:45 AM #5

Yes, hitting Y suggests a positive outcome.

I
Ix_Tha_God_xI
Member
96
10-18-2018, 08:05 AM
#6
Also, should I configure the boot device to the storage where the operating system will be installed or the thumb drive containing the installation media? Edited March 28, 2023 by ReNForce
I
Ix_Tha_God_xI
10-18-2018, 08:05 AM #6

Also, should I configure the boot device to the storage where the operating system will be installed or the thumb drive containing the installation media? Edited March 28, 2023 by ReNForce

C
chris66072
Member
156
10-18-2018, 09:40 AM
#7
You start by inserting the flash drive, which will ask you to choose the one for Windows installation. Usually I use the advanced setup in the installer because it gives a direct way to pick the desired drive.
C
chris66072
10-18-2018, 09:40 AM #7

You start by inserting the flash drive, which will ask you to choose the one for Windows installation. Usually I use the advanced setup in the installer because it gives a direct way to pick the desired drive.

T
199
10-21-2018, 03:52 AM
#8
Thanks! I'm ready to help right away.
T
the_one_waffle
10-21-2018, 03:52 AM #8

Thanks! I'm ready to help right away.