Is this an onboard controller or an external? A typical external RAID controller (and some internal) have a BIOS that loads on POST which may show you whether it's active or not.
Otherwise, most BIOS post messages display the IRQ info of onboard components during boot so you should technically see a SATA/SAS/RAID controller there.

I'd suspect the drive or corrupt boot loader first.

What OS is this?

That's extremely helpful, first time hearing about this tool.

Thanks for sharing

But like anything - this could grow through the use of other compromises for privilege elevation, and bam - pown'ed.

Claiming this is UEFI issue is false. This maybe an HP + UEFI issue, but it is not a UEFI issue.

We use Clonezilla at one client for applying the desktop images and we run 100% UEFI.
Those systems are all Dell though. We do not do any cloning at any of our clients that have HP systems.

@connorsoliver I was wondering the same thing. I know we can download equivalents on our phones, but didn't think it was an option on the BIOS.

@mary said in BIOS Configurations - CompTIA A+ 220-901 220-902 Video Training by Prof. Messer:

If your graphics card was failing would that show up in the diagnostics as well? This will be a great tool if you suspect hardware failure. As to the fake BIOS, if you make changes in the virtual environment will it show you a reflection of those changes?

Depends on the diagnostics. As external hardware, diagnostics of it tend to be more limited.

@Pete-S said in BIOS and UEFI - CompTIA A+ 220-901 220-902 Video Training by Prof. Messer:

@travisdh1 said in BIOS and UEFI - CompTIA A+ 220-901 220-902 Video Training by Prof. Messer:

@Pete-S How long did you spend holding UV lights over those chips? Me = many hours, way to long.

Haha, spent a lot of time doing that. But I had an UV eraser which basically meant you could put it in and walk away.

I spend enough time doing it so I could immediately tell that the EPROM I posted a pic of above, is made by Texas Instruments (from the logo) and it's 256 kbit (from 27C256) so 32 kilobyte memory.

@coliver said in Sysprep won't run if a drive has Bitlocker enabled:

@Dashrender said in Sysprep won't run if a drive has Bitlocker enabled:

@coliver said in Sysprep won't run if a drive has Bitlocker enabled:

@dbeato said in Sysprep won't run if a drive has Bitlocker enabled:

@coliver Did you setup a Microsoft account on them?

No domain joined machines.

Are you sure Bitlocker isn't on, just not activated?

I'm not sure what you mean? Bitlocker is a part of the operating system... you need to turn it on to enable encryption. So if you're asking if it is installed the answer is yes. If you're asking if it is enabled the answer is no.

Bitlocker has three states, as far as I can tell

Bitlocker Off Bitlocker On, but not activated - not encrypting drive Bitlocker activated

In my experience, a BIOS based machine puts Windows 10 into option 1 above.
My recent experience has shown that machines with UEFI and Secure Boot enabled that Windows 10 puts the system in option 2 or 3 depending on setup.
If you add a Microsoft Account while going through OOBE, the Windows will create a recovery key for Bitlocker, save it to your OneDrive account, and use option 3.
If you add a local account during OOBE, Windows will put the system into option 2.

Some folks are having a bad day. A real bad day.

Yeah I was wondering how he was going to handle that ALL manufacturers today are pretty much guaranteed to be doing some sort of tracking. Granted that tracking is so they can make the product better.

The author also didn't mention if they did a fresh install of Windows when they received the machine - to me that was his first downfall, but the fact that Lenovo has already shot itself in the foot, this doesn't help.

It's apparently a sporadic issue with Server 2012 r2 or Windows 8.1 running on Hyper-V on Windows 8.1/Server 2k12 R2 with Generation 2 VMs and secure boot. Secure boot needs to be disable for some updates. All expect for 3 out of the 98 were failing. Odd thing is there are four other 2k12 r2 Gen 2 VMs on the host that had no issues with the windows updates. Disabled Secure boot on the VM and it worked fine.