Linux and Windows 8 Fast Startup


Recommended Posts

I thought this would be worth linking here, since it might be relevant to some Neowinians:

The new Fast Startup feature of Windows 8 puts the filesystem's integrity at risk if other operating systems are used to write to Windows partitions. Data loss is particularly likely with dual-boot configurations that involve Linux and Windows 8.

Full Article.

TL;DR If you're using the Windows 8 Fast Startup option and dual boot with another OS, consider the Windows 8 partition(s) to be read-only and/or disable fast startup. Writing to a Win8 partition from Linux can cause the files to go missing on Win8 and/or be corrupted due to the way that fast startup works. The NTFS-3G driver has not yet been updated to detect fast-boot, so will mount as read/write on many distros (including Debian and Ubuntu). Apparently a fix is in Debian testing, but this means that Stable users won't see it for a while yet.

Link to comment
https://www.neowin.net/forum/topic/1130568-linux-and-windows-8-fast-startup/
Share on other sites

I disabled fast boot when I was running 8 anyway, with an OS as young as 8 there is always going to be bugs that need a reboot to fix, fast boot means you have to reboot on top of normally powering on in the morning, where normally a shutdown and power on would have done the same job without fast boot

Of course, if you've disabled Hibernation, this need not apply. Still, a good article for the people that use this option.

Correct me if I'm wrong, but aren't fast startup and hibernation different things? I mean they accomplish similar goals, but they're not the same thing. Disabling hibernation != disabling fast startup. NTFS-3G already detects hibernation and only mounts an NTFS partition as read-only if Windows is hibernating, but the issue is that it doesn't do the same thing for fast startup (yet), which means that there's a risk.

Correct me if I'm wrong, but aren't fast startup and hibernation different things? I mean they accomplish similar goals, but they're not the same thing. Disabling hibernation != disabling fast startup. NTFS-3G already detects hibernation and only mounts an NTFS partition as read-only if Windows is hibernating, but the issue is that it doesn't do the same thing for fast startup (yet), which means that there's a risk.

The Fast Startup option uses Hibernation, or its own form of it. Disabling hibernation completely disables the fast startup option in Windows 8. I think the Fast Startup option is using the same hiberfile.sys that hibernation is using. Running the command "powercfg -h off" in the command prompt removes this option and deletes the hiberfile.sys. Fast Startup no longer becomes an option. You can achieve the same results this way of disabling Fast Startup (and saving space now that you no longer have a hiberfile.sys).

"The Fast Startup feature creates an issue because it doesn't shut Windows 8 down completely but switches it to a special hibernation state instead ? although it looks like it has been freshly booted when switched back on because all applications have been closed."

Also, found on Eightforums.com "Because if you disable Hibernate, Fast Startup also disabling automatically" http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html (Option 3)

The Fast Startup option uses Hibernation, or its own form of it. Disabling hibernation completely disables the fast startup option in Windows 8. I think the Fast Startup option is using the same hiberfile.sys that hibernation is using. Running the command "powercfg -h off" in the command prompt removes this option and deletes the hiberfile.sys. Fast Startup no longer becomes an option. You can achieve the same results this way of disabling Fast Startup (and saving space now that you no longer have a hiberfile.sys).

"The Fast Startup feature creates an issue because it doesn't shut Windows 8 down completely but switches it to a special hibernation state instead ? although it looks like it has been freshly booted when switched back on because all applications have been closed."

Also, found on Eightforums.com "Because if you disable Hibernate, Fast Startup also disabling automatically" http://www.eightforu...indows-8-a.html (Option 3)

Ah okay, interesting. Thanks for the info :)

Is anyone able to verify this? If so, will pass the word along on the front page.

h-online.com is the English site of heise.de. Their magazines have a good reputation for actually researching what they're writing about.

That said independent confirmation could be good. Surely someone here has a Windows 8/Linux dual-boot config.

Is anyone able to verify this? If so, will pass the word along on the front page.

I'm not sure if files don't get lost or corrupted reliably, but I was not able to reproduce this with Windows 8 and Debian 7 dual-booting in VirtualBox. (I don't run Windows natively, but I don't see how a native installation would make any difference.) My log of commands I ran in Windows and Debian to try to reproduce this problem, as well as their output, is below.


PS C:\Users\xorangekiller> mkdir Desktop\rar


Directory: C:\Users\xorangekiller\Desktop


Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 1/14/2013 2:51 PM rar


PS C:\Users\xorangekiller> echo rar > Desktop\rar.txt
xorangekiller@pigeonhole:~$ sudo mkdir /mnt/rar
xorangekiller@pigeonhole:~$ sudo parted -l
Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sda: 8590MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 1049kB 8186MB 8185MB primary ext4 boot
2 8187MB 8589MB 402MB extended
5 8187MB 8589MB 402MB logical linux-swap(v1)


Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sdb: 32.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 1049kB 368MB 367MB primary ntfs boot
2 368MB 32.2GB 31.8GB primary ntfs


xorangekiller@pigeonhole:~$ sudo mount -t ntfs /dev/sdb2 /mnt/rar
xorangekiller@pigeonhole:~$ mkdir /mnt/rar/rar
xorangekiller@pigeonhole:~$ echo rar > /mnt/rar/rar.txt
xorangekiller@pigeonhole:~$ ls -l /mnt/rar/ /mnt/rar/Users/xorangekiller/Desktop/
/mnt/rar/:
total 2359737
-rwxrwxrwx 1 root root 398156 Jul 25 23:44 bootmgr
-rwxrwxrwx 1 root root 1 Jun 2 2012 BOOTNXT
drwxrwxrwx 1 root root 4096 Jan 4 00:53 Config.Msi
lrwxrwxrwx 2 root root 60 Jul 26 03:22 Documents and Settings -> /mnt/rar/Users
-rwxrwxrwx 1 root root 2147483648 Jan 14 14:30 pagefile.sys
drwxrwxrwx 1 root root 0 Jul 26 03:33 PerfLogs
drwxrwxrwx 1 root root 4096 Oct 27 11:45 ProgramData
drwxrwxrwx 1 root root 4096 Nov 2 17:46 Program Files
drwxrwxrwx 1 root root 4096 Dec 12 21:11 Program Files (x86)
drwxrwxrwx 1 root root 0 Jan 14 14:38 rar
-rwxrwxrwx 1 root root 0 Jan 14 14:38 rar.txt
drwxrwxrwx 1 root root 0 Sep 6 21:44 $Recycle.Bin
-rwxrwxrwx 1 root root 268435456 Jan 14 14:30 swapfile.sys
drwxrwxrwx 1 root root 4096 Oct 27 11:38 System Volume Information
drwxrwxrwx 1 root root 4096 Oct 15 00:37 Users
drwxrwxrwx 1 root root 24576 Jan 4 00:52 Windows

/mnt/rar/Users/xorangekiller/Desktop/:
total 1
-rwxrwxrwx 1 root root 282 Dec 12 21:55 desktop.ini
drwxrwxrwx 1 root root 0 Jan 14 14:39 rar
-rwxrwxrwx 1 root root 0 Jan 14 14:39 rar.txt

xorangekiller@pigeonhole:~$ sudo umount /mnt/rar
PS C:\Users\xorangekiller> ls Desktop


Directory: C:\Users\xorangekiller\Desktop


Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 1/14/2013 2:51 PM rar
-a--- 1/14/2013 2:56 PM 12 rar.txt


PS C:\Users\xorangekiller> ls C:\


Directory: C:\


Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 7/26/2012 3:33 AM PerfLogs
d-r-- 11/2/2012 5:46 PM Program Files
d-r-- 12/12/2012 9:11 PM Program Files (x86)
da--- 1/14/2013 3:01 PM rar
d-r-- 10/15/2012 12:37 AM Users
d---- 1/4/2013 12:52 AM Windows
-a--- 1/14/2013 3:01 PM 4 rar.txt


[/CODE]

VirtualBox is OK for trying out new OS's w/o risk, but it's not quite like the real deal. Remember those anti-Windows 8 You Tube videos? Many were using VBox for those propaganda videos, making Windows 8 CP & RP look poorly, to turn users against 8. Looking at some of the videos closely revealed this.

I have dual boot, & I also have 4 working computers, so actually I can have Windows 8 & Zorin OS on at the same time, in real life speed. Plus on my main two computers, I have SSD's (a 180GB Intel 330 & 128GB M4), so all of that fast boot gimmick stuff isn't needed. I have Windows 8 Pro on two computers, one a "fast boot", on a WD RE4 & the other on the Intel 330, it's pointless to state which is the fastest.

However, I've yet to try dual boot Windows 8 & Zorin OS, now I have a reason to, to see which boots fastest on the same hardware. That in itself doesn't make either better than the other, though. Thing is, all one has to do is place their OS in hibernation, which is what is happening with 8, & see which is the fastest. It may or may not be Windows 8 that's truly the fastest starter.

Cat

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!