No splash screen at daily startup

This is the one with the yield sign, the properties say (obviously) the device is disabled:

This is the "copy", according to the properties, this device is not connected:

Some more information regarding the splash screen issue:
I have noticed that, when I hold the "Volume Up" control (in my case "Fn+F8") while I press the power button (I read this somewhere online, can't remember where), the laptop boots up immediately.
However, the Samsung splash screen stays there for quite a while.

I also noticed that, when the machine refuses to boot up, it seems to be the HDD that does not start right away (that is what I assume when I watch the lights).

Does any of that make any sense to the more knowledgeable among you?

dalchina please find solutions for mrfdes

Hi,
thank you for your input.

I have downloaded th ISO and put it onto a DVD.

I set the boot order to boot from DVD, but apart from the fact the machine booted up much slower than usual, it booted up in Windows like it always does.
I did not see anything different happen, unless I missed something, of course.

Anyway, thank you for this.

dalchina said:

Did you see this when you booted from your DVD?

Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

No, unfortunately I saw my usual normal desktop.

Did you burn the iso to your DVD or simply copy the file to it as a data disk?
You need to do the first. The second does not create a bootable DVD.

Yes, I used the first method and have a bootable disk.

- means you didn't boot from the DVD, but from your hard disk- exactly what we're trying not to do.

Or have you not changed the boot order in BIOS (as is always required and has been required for many years) so the PC looks at your DVD drive before the hard disk?

I did change the boot order, I also tried from a USB stick, it seems to be ignored by the laptop.

e.g.
How To Change the Boot Order (Boot Sequence) in BIOS


Again:

And, I forgot to mention that, unfortunately I do not have a spare HDD at the moment.

Thank you for your help so far.

I assume it must be part of my symptoms, if, in spite of having reversed the boot order and having bootable media in the laptop, it still boots up in the usual way.

Furthermore, I have a USB DVD drive connected to my laptop, which shows up in the Device Manager, but not in the BIOS, same thing when I connect a USB stick.

The first thing I thought about was looking for a newer BIOS version, at the moment I have American Megatrends P09ABE, 04/07/2013 on a Samsung NP350V5C motherboard, but neither the Samsung nor the AMI websites are very helpful nor user friendly.

Here is what msinfo32 shows:

OS Name Microsoft Windows 10 HomeVersion 10.0.15063 Build 15063Other OS Description Not AvailableOS Manufacturer Microsoft CorporationSystem Name ACHTLAPTOPSystem Manufacturer SAMSUNG ELECTRONICS CO., LTD.System Model 350V5C/351V5C/3540VC/3440VCSystem Type x64-based PCSystem SKU P09ABE.012.CPProcessor Intel(R) Pentium(R) CPU B970 @ 2.30GHz, 2300 Mhz, 2 Core(s), 2 Logical Processor(s)BIOS Version/Date American Megatrends Inc. P09ABE, 04/07/2013SMBIOS Version 2.7Embedded Controller Version 9.00BIOS Mode UEFIBaseBoard Manufacturer SAMSUNG ELECTRONICS CO., LTD.BaseBoard Model Not AvailableBaseBoard Name Base BoardPlatform Role MobileSecure Boot State OnPCR7 Configuration Binding Not PossibleWindows Directory C:\WINDOWSSystem Directory C:\WINDOWS\system32Boot Device \Device\HarddiskVolume2Locale United KingdomHardware Abstraction Layer Version = "10.0.15063.0"Username Achtlaptop\frank_000Time Zone GMT Summer TimeInstalled Physical Memory (RAM) 6.00 GBTotal Physical Memory 5.89 GBAvailable Physical Memory 3.06 GBTotal Virtual Memory 6.26 GBAvailable Virtual Memory 3.47 GBPage File Space 384 MBPage File C:\pagefile.sysDevice Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usableHyper-V - VM Monitor Mode Extensions NoHyper-V - Second Level Address Translation Extensions NoHyper-V - Virtualisation Enabled in Firmware NoHyper-V - Data Execution Protection Yes

Especially the Device encryption support bothers me, that seems to be somewhat BIOS related.
Hope I have given you some more clarity with this.

Thank you for your help and advice.