It should also be possible to use as boot volumes (e.g. install and boot Windows from ReFS partitions)?
From the info I have, I assume that with v3 driver ReFS can be used on both BOOT and SYSTEM partitions. Also Windows 10 Setup (WinSE) has full ReFS v3 driver support now.
How to verify ReFS version used on your drive: Code: C:\Users\Final>fsutil fsinfo refsinfo D: REFS Volume Serial Number : 0xffffffffffffffff REFS Version : 1.1 Number Sectors : 0x00000001d1bc0000 Total Clusters : 0x0000000003a37800 Free Clusters : 0x0000000000210c58 Total Reserved : 0x0000000000000000 Bytes Per Sector : 512 Bytes Per Physical Sector : 512 Bytes Per Cluster : 65536 Checksum Type: CHECKSUM_TYPE_CRC64
error in here when I try to run the vbs in 11082 Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")
Formatting with ReFSv1 and ReFSv3: Code: format D: /fs:refsv1 format D: /fs:refs You can add manually the string: Code: %windir%\system32\wbem\refs.mof to: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wbem\CIMOM] value: Autorecover MOFs Note: In the list (of MOFs) there is one (actually the 1st to be exact) item starting with blank line, Windows will scream about that, just delete that item.
Pack updated in 1st post... Changes: 1. Now you are able to format ReFSv3 in client OSes. 2. Now you can access ReFSv3 volumes.
i have heard about reFS many years, but i have never looked at it...is it better than ntfs or what? should i format my harddrive in reFS and install windows again perhaps? will the usbstick boot and install windows if i do that?
I hope that this version is acceptable, because in version in Server 2012 R2 was nothing but problems. While working OK itself, lots of apps had serious problems with accessing such volumes across network. Eventually had to move to NTFS
Every time I try to copy the urefs.sys files, it says I need permissions but still denies me. Changed myself to be the owner of the files and give my user full control, still denies. Any ideas?