I followed your howto.txt instructions step 1 & 2, but step 3 (run Add_AutorecoverMOFs_Only.vbs_), i'm getting the error I tried to format an NTFS drive after rebooting (ignoring the error message), and format failed as shown below: PC:\Windows\system32> format E: /fs:refsThe type of the file system is NTFS.The new file system is REFS.Enter current volume label for drive E: NEW WARNING, ALL DATA ON NON-REMOVABLE DISKDRIVE E: WILL BE LOST!Proceed with Format (Y/N)? yFormatting 39.1 GBReFS file system is not supported on this device.Format failed. please advice how i can proceed. thanks.
For formatting TEMPORARILY import this in the registry (and delete it after format): Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT] "AllowRefsFormatOverNonmirrorVolume"=dword:00000001 The REG is in the "Allow" directory of the pack. Otherwise on Windows_Clients, user is able to ReFS format only the mirrored volumes (except Windows 8-0). Don't forget to delete the entire "MiniNT" key (after the format), otherwise your OS will be considered as WinPE (WinRE). BTW: For loading the driver, reboot is required. Instead running VBS, just open regedit, go to: Code: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM Double click on item: Code: Autorecover MOFs (ERASE THE EMPTY 1st line in the list (otherwise, you will get error)) and add this at the end of the list: Code: %windir%\system32\wbem\refs.mof "refsv1.mof" should be already in the list. Also you can split VBS to two files (according the horintal line in the middle of the VBS) and run them separatelly.
With this package it will be good (not mandatory but still) to add (to append to value-list NOT to overwrite value-list) three values to two registry keys (two with restricted rights). Who can make the script to make it? Code: The key below isn't protected by OS: 1. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wbem\CIMOM] Autorecover MOFs = %windir%\system32\wbem\refs.mof %windir%\system32\wbem\refsv1.mof The keys below are protected by OS: 2. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009] and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\CurrentLanguage] and [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\009] and [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\CurrentLanguage] Counter = 7424 ReFS 7538 Log fill percentage Help = 7425 Information on the ReFS file system performance counters. 7539 The fill percentage for the ReFS log.
Can W10_RS1 be finally installed on and booted from ReFS? I guess most people simply don't realize the problem for what it is when they face it (or the caching/flushing algos of my specific SSD model also "help" the odds of this happening) but sometimes I do have "silent corruption" after random system crashes (usually caused by specific VGA driver versions paired with some specific games/applications and settings), although I usually realize this too late (hence the silent name: it doesn't scream until you step on it). So, it would be nice to work with a filesystem under the OS files which "either works or fully breaks" like Btrfs or ZFS on Linux (so I can be sure I don't make a backup from a corrupted state which is obviously not a nice thing... but help me realize the corruption sooner).
Why? I know I can check most of the Windows files with DISM and even consumer grade content managers like Steam and Origin offer checksum verification on their files (they seem to think it's important enough for games while few professional softwares have these kind of self-check/repair facilities), but there are still some other temporal/work files residing on that filesystem (either because you are lazy and leave it at default, or out of necessity / forced presets, or you deliberately want them on the fastest drive for the day which happens to be your SSD with the OS, not your HDD storage pool, etc). And online real-time checksuming is superior to the examples I gave (a figurative question to illustrate this: How frequently should I run these manual checks? One in every month, week, or day, or hour...? One after every Windows boot and once before loading the game or other software? What about complicated softwares which I can't check so easily?) I think it's equally important for system drivers and I am even leaning toward to say it might be slightly more important.
I have all drives ReFS v1-1 (formated in Windows 8-0) now. When I will buy new big drive, I will reformat them to ReFS v3-1.
To use integrity streams, format drive like this: Code: format X: /fs:refs /i:enable format X: /fs:refsv1 /i:enable
I'm getting a "format failed" on 14393 after the format completes Code: C:\Windows\system32>format E: /fs:refs /q The type of the file system is REFS. WARNING, ALL DATA ON NON-REMOVABLE DISK DRIVE E: WILL BE LOST! Proceed with Format (Y/N)? y QuickFormatting 931.5 GB Volume label (32 characters, ENTER for none)? Creating file system structures. Format complete. 931.5 GB total disk space. 931.5 GB are available. Format failed. Not sure why it completes then fails... probably followed the guide incorrectly?
Any ideas on the difference between 3-0 and 3-1? I created some volumes on 10586 with the TP4 pack and now on 14393 they are shown as 3-1