Can't Turm off Fast Boot and/or Hibernation(?)

quarkrad · 20 Sep 2018

Here are the the two time images

Can't Turm off Fast Boot and/or Hibernation(?)-linuxtime.png

Can't Turm off Fast Boot and/or Hibernation(?)-win10time.png

quarkrad · 20 Sep 2018

I keep reading how Fast Boot was enabled in 1803, despite settings, so .... perhaps a work around for me, if I cannot turn it off, is to go back to 17XX. I guess by not having the latest and dearest I could be vulnerable net wise but it's looking more like I might not have choice. If I want to dual boot then I might have to run 17xx and not be net connected - very inconvenient but I'll have to use my linux side to download things I need on win10. I also think the reason option appear to be missing is that I'm running win Home whereas web site examples could be base on win Pro.

zbook · 20 Sep 2018

1) Run the sfc /scannow command to make sure the corrections to the operating system were not temporary.

2) Run the BETA log collector and post a zip into this thread:
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract > open)

quarkrad · 20 Sep 2018

The sfc scan didi not show any issues - everything was OK. Hopefully the attached is OK for you to read.

quarkrad · 20 Sep 2018

Should I start a new thread on reverting back to 17XX, and what updates I need to keep me safe ongoing, or shall I stick with this thread and ask this question if I find I cannot turn off FastStart? Despite configuring everything to turn it off (including reg entry) does the fact that it starts to boot in less than 1 sec after the grub screen indicate to you that it is FastStarting?

zbook · 20 Sep 2018

1) Open device manager > click view > show hidden devices > manually expand all rows > look for any row displaying a yellow triange with black exclamation mark or unknown device > post an image into the thread

2) Uninstall Driver booster 5, Iobit

3) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

4) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

5) Open disk management > widen each of these two columns so that the characters in each row are in full view and no letters are cut off (Status and Volume) > post an image into the thread
Disk Management - How to Post a Screenshot of | Windows 10 Tutorials

6) Download and install HD Tune (free or trial edition) (test all drives)
Post images of the results for each of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

Code:

TimeZone                : GMT Standard Time(GMT+01:00)

Code:

Unknown USB Device (Device Descriptor Request Failed) USB\VID_0000&PID_0002\5&212AC8FC&0&7 43

Code:

Event[4640]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T06:27:43.786
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The driver detected a controller error on \Device\Harddisk5\DR6.

Code:

Event[4428]:
  Log Name: System
  Source: Disk
  Date: 2018-09-14T19:11:00.974
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The driver detected a controller error on \Device\Harddisk5\DR12.

Code:

Event[4659]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:43:54.839
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR7 during a paging operation.
Event[4660]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:47:04.555
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
Event[4661]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:47:04.555
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
Event[4662]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:47:06.420
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
Event[4663]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:47:06.420
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR8 during a paging operation.
Event[4664]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:48:00.631
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR9 during a paging operation.
Event[4665]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:01.118
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR10 during a paging operation.
Event[4666]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:02.985
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR10 during a paging operation.
Event[4667]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:02.985
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR10 during a paging operation.
Event[4668]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:16.987
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR11 during a paging operation.
Event[4669]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:17.174
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR11 during a paging operation.
Event[4670]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:17.362
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR11 during a paging operation.
Event[4671]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:49:17.549
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
An error was detected on device \Device\Harddisk6\DR11 during a paging operation.

Code:

Event[4679]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:55:23.317
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The IO operation at logical block address 0x360 for Disk 6 (PDO name: \Device\00000083) was retried.
Event[4680]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:55:23.332
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The IO operation at logical block address 0x320 for Disk 6 (PDO name: \Device\00000083) was retried.
Event[4681]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:55:23.348
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The IO operation at logical block address 0x320 for Disk 6 (PDO name: \Device\00000083) was retried.
Event[4682]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:55:43.737
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The IO operation at logical block address 0x143a0 for Disk 6 (PDO name: \Device\00000083) was retried.
Event[4683]:
  Log Name: System
  Source: Disk
  Date: 2018-09-15T07:56:08.727
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-4UI7ED1
  Description: 
The IO operation at logical block address 0x101 for Disk 6 (PDO name: \Device\00000086) was retried.

Code:

Event[4644]:
  Log Name: System
  Source: Service Control Manager
  Date: 2018-09-15T06:41:19.934
  Event ID: 7040
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-21-10857401-3704263751-77058797-1001
  User Name: DESKTOP-4UI7ED1\dad
  Computer: DESKTOP-4UI7ED1
  Description: 
The start type of the Windows Time service was changed from disabled to demand start.
Event[4645]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2018-09-15T06:41:19.982
  Event ID: 158
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.
Event[4646]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2018-09-15T06:41:20.060
  Event ID: 37
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->13.79.239.69:123).
Event[4647]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2018-09-15T07:41:20.374
  Event ID: 1
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Time
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The system time has changed to ?2018?-?09?-?15T06:41:20.375027500Z from ?2018?-?09?-?15T05:41:20.076086000Z.
Change Reason: An application or system component changed the time.
Event[4648]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2018-09-15T07:41:20.375
  Event ID: 35
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->13.79.239.69:123) with reference id 1173311245. Current local stratum number is 3.
Event[4649]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2018-09-15T07:41:20.373
  Event ID: 1
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Time
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The system time has changed to ?2018?-?09?-?15T06:41:20.376535400Z from ?2018?-?09?-?15T06:41:20.377503700Z.
Change Reason: An application or system component changed the time.
Event[4650]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2018-09-15T07:41:21.462
  Event ID: 158
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-4UI7ED1
  Description: 
The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.

MeAndMyComputer · 20 Sep 2018

On the time difference, it may not be unusual but there is a way to correct it.
A couple of years ago I was dual booting with Win10 Pro & Linux and there was a time difference between them: I don't recall if it was one hour: but one of them booted up at the right time, the other one was different.
Unfortunately I don't recall how I was able to fix it but there is a solution.

I have reverted back to only Win10 Pro.
--- If I was younger I would have stayed with learning Linux as well but I like Windows 10 and am familiar with how to keep my computer secure and well maintained pretty naturally.

I wish I could help you on the solution but you can ask what the solution is on Linux help forum or someone who knows what to do right here in our Windows 10 forum.

I just did some investigation on why your fast startup doesn't stay disabled: is that what your are saying?
I didn't see anything in which 1803 doesn't allow fast startup to be disabled and some of those articles included users having SSD.
--- You might want to disable Secure boot as well.

On your Samsung SSD, go to their help page or whatever it's called and ask the question: why is it when you disable Fast Boot, the SSD still boots up as fast as you mention.
--- I would imagine your Samsung SSD has a utility program to diagnose your SSD and let you know details about it's settings etc.

I have a Crucial SSD and I have used their diagnostic utility just to see what it shows.
--- It wasn't because I had any issues, I just wanted to know.

quarkrad · 20 Sep 2018

Sorry I've been a long time. To make this simple I have disconnect my 2nd drive so all I have now is the Samsung SSD. Attached images as requested - I hope they are OK. I have uninstalled Drive Booster and deleted entries in registry. To be honest I wasn't sure what to do with the rest of the thread re coding. I was interested in the first bit of code where it says GMT Standard Time (GMT+01:00). When I type timezone in Powershell it says GMT Standard Time, (UTC+00:00) - so it looks I'm running coordinated time.
GMT Standard Time(GMT+01:00)

zbook · 20 Sep 2018

1) For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files

2) For unknown devices in device manager run through the steps in these links:
How to easily find drivers for Unknown Devices in Windows | PCWorld
https://www.howtogeek.com/193798/how...evice-manager/

3) Make a backup image using Macrium (free edition), or any other imaging software (Acronis, Aoemi, EaseUS, Paragon, etc)
(Make the backup image after all of the steps in this post)
Several images can be made, for example one image can be saved at the moment everything is ok with the operating system, drive file system, applications, files, etc. and a second image can be updated with incremental weekly backups. Then if there are problems there is always one image that can be used. There are many methods to use images and it will be user preference.
Macrium is widely used and highly recommended in Ten Forums.
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect | Windows 10 Tutorials

Save the backup image to another drive or to the cloud.
With a backup image you should have options for unexpected boot failure, ransomware, operating system and registry corruption, drive failure, etc.

4) Increase the free space on the Windows drive to > 30 GB

5) For startup and recovery system failure:
a) uncheck automatically restart
b) reboot
It can be easy to miss bsod if automatically restart is checked.
With automatically restart unchecked if there is a bsod you should see a window with a bugcheck and : (
Sometimes it may display a misbehaving driver in the form *.sys.
At the beginning of any bsod there is a % counter.
If you see this counter allow it to rise to 100 % before rebooting.

quarkrad · 21 Sep 2018

Thank you. I am not in a position to make an image yet because I still have this fundamental problem of being unable to turn off Fastboot/hibernation. I have made a few tweaks to my bios and the result, although subjective, is that windows is booting even faster. Also, increasing free space to >30 GB is not possible because I only have 49GB for the whole of C drive. Many sites suggest, with a SSD, 25% free space is conservative due to the over provisioning of a modern SSD. At the moment my free space is about 38% so I would have thought I am within limits. How does the amount of free space effect the turning off, or on, of FastBoot/hibernation?