The Oven

Project World => Win10PE SE HomePage => Topic started by: Atari800xl on October 05, 2017, 12:07:04 PM

Title: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: Atari800xl on October 05, 2017, 12:07:04 PM
...
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 05, 2017, 06:11:02 PM
The experimentation is in progress  :wink:

[attach=1]
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: Atari800xl on October 05, 2017, 07:18:42 PM
...
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 05, 2017, 11:21:00 PM
it doesn't seem like 1709 provides a lot of new stuff, but I'm sure you will be a far better judge of that (eg. ReFS 3.3, I can't tell how significant that is).

That actually kind of sucks..  :sad: It is a feature "Removal" not addition.. You will no longer be able to format ReFS partitions by changing the registry and allowing yourself to do so.  This will no longer be possible in ReFS 3.3 - Paving way for the new 'Windows Pro for Workstations" - Which I think will have the system partition as ReFS??, which you will have to pay extra for  :wink:

ReFS 3.3: https://support.microsoft.com/en-us/help/4034825/features-that-are-removed-or-deprecated-in-windows-10-fall-creators-up (https://support.microsoft.com/en-us/help/4034825/features-that-are-removed-or-deprecated-in-windows-10-fall-creators-up)

I currently run ReFS drives with Storage Spaces virtual raid.  Very reliable, and actually out performs hardware raid. Works through usb as well as sata and the pool can be managed. 3-way mirror(You can drop random size drives in any way you can and they get added)  :great: I wonder if we could keep 3.2 or make a script to swap it back? I'll make a thread later on for that.  Changing the registry value in current builds adds the option to the system format > dropdown screen for choosing file system e.g fat32, exFat, NTFS, ReFS, when formatting something.

When ReFS is primetime chkdsk will be obsolete, and you will be able to pull your power cord out in the middle of a system update without messing up your os....

------------------
Enable ReFS formatting in Win10PESE ** Edited to prevent automatic ReFS upgrade - This maintains compatibility of older filesystems with their hosts when accessed with PE.
------------------
Code: [Select]
RegHiveLoad,Tmp_System,%RegSystem%
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\MiniNT,AllowRefsFormatOverNonmirrorVolume,1
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableLastAccessUpdate,1
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableVolumeUpgrade,1
RegHiveUnLoad,Tmp_System

Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: APT on October 06, 2017, 10:10:12 AM
...
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: s1ave77 on October 06, 2017, 11:44:48 PM
@bob.omb A>lthough it might suck, it's understandable move to position Pro against the new Pro for Workstation SKU, the latter supports all mentioned features natively. Might be worth a try.

It's actually a Pro with changes to support 4 CPU sockets, 2 TB RAM, persistant memory and REFS.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 07, 2017, 09:03:13 AM
Yes but who knows how the change is going to affect PE builds.  There is a possibility pro for workstations wont be able to be ported to PE if the filesystem does happen to be ReFS on the system partition.  If that's the case 1703 will be the last version able to manipulate ReFS which makes it the last universal ISO.  We'll see what happens =)
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 07, 2017, 12:05:27 PM
Only from some readings, nothing tested.
With ReFS 3.2,  it does not seem possible to read a 3.3 ReFS volume
So downgrade to ReFS 3.2 is not the way to go. A Windows 1709 with ReFS 3.3 volumes would be unreadable.
For the Creation, format ability, as written by s1ave77, we need to use, Win10 Pro Workstation or enterprise.
Perhaps the change can be ported in a Win10PE build with another edition (productpolicy?)

By cons, I wonder if there is a possibility (registry) not to Auto Upgrade volumes to 3.3
This would be a concern if, using a WinPE 1709 with ReFS 3.3, the host volumes were upgraded.
They would become unreadable then in the host OS.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 07, 2017, 02:35:10 PM
 :ohmy: This is dangerous I need to update my release immediately.. :ohmy: (fix below) if someone uses current Win10PE on Server 2016 or Win8 machine with ReFS volumes (Those use 3.1)they will break the volumes. (You may want to add this line to core builds registry even if you don't enable formatting just to be safe)

** This seems like a bad idea on Microsofts part, forced upgrades without the knowledge of the user for any existing ReFS systems with 0 compatibility, only conversion.. 

By cons, I wonder if there is a possibility (registry) not to Auto Upgrade volumes to 3.3

Looks like there's a key in current builds that prevents upgardes from 3.1 to 3.2 from automatically happening. Hopefully this key will still be available in 3.3

Registry to prevent upgrade. It needs to be set before connecting.
Code: [Select]
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableVolumeUpgrade,1

Source: https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_files/connecting-refs-v231-volume-to-windows-10-build/8bb1cdcb-fbf8-4c52-b763-bb4714613525?auth=1 (https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_files/connecting-refs-v231-volume-to-windows-10-build/8bb1cdcb-fbf8-4c52-b763-bb4714613525?auth=1)

I updated the codebox in Reply #3, to add this line in case anyone doesn't scroll down this far to see the addition. 

Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: Lancelot on October 08, 2017, 08:00:30 AM
Following things related to ReFS

I feel It will be useful to add all ReFS related things to a plugin:

Added new plugin to server:
\Downloads\DriversY\ReFS

ps: not related but also added these:
\Downloads\ComponentsY\Tweaks Explorer\Exp IconSize
\Downloads\AppYGS\Supplementary\Tweaks\DesktopOK

:turtle:
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 08, 2017, 02:57:18 PM
I have a little concern.. Win10PE is able to access ReFS and "Read/Write" even older volumes,  WITHOUT upgrading, yet autoupgrade is set default by MS,  It can do this whether we enable ReFS "Formatting" or not.

This means any Win10PESE build ever will break an ReFS drive(made with Server 2012/8.1/**Server 2016**) by default

Was thinking....Maybe,
Code: [Select]
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableVolumeUpgrade,1

Should be hardcoded in build??? And optional checkbox on ReFS plugin shoud be to "Enable Automatic Upgrade of ReFS Volumes" (With a warning that ReFS isn't backwards compatible)???

This would need to be used if you decide to go that route.
Code: [Select]
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableVolumeUpgrade,0

Even though this is the way windows normally works, PE users are MUCH MORE likely to attempt to access volumes on other systems.

BTW - Not sure if you want to hardcode, maybe not, but thanks for putting so much time into this,  I know you are busy but you've been doing a lot here thank u.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: Lancelot on October 08, 2017, 05:00:00 PM
Hi bob.omb

updated
DriversY\ReFS
I feel more informative and secure now.  :wink:

*
updated
Build\"Project Medicine" plugin with line:
Code: [Select]
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\FileSystem,RefsDisableVolumeUpgrade,1
to protect end users.

=>
I guess ReFS is feature of Win8 and later,
So I update both plugin to add ReFS registry to Win8SE, Win8.1SE, Win10PESE and later ..

Fix me if required.

**
@bob.omb
Tip:
"exact and secure update" preserves settings on plugins.
just make sure you have the latest
Utils\Plugin Manager
and
Utils\Update XXXX (Exact and Secure)
from server
(small green download button on both plugins)

:turtle:
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 08, 2017, 05:12:38 PM
[attach=1]

Windows 8 no ReFS - Starts at 8.1 - Yes would be wise to put in 8.1 thru future builds unless there's a reason to switch it back on. (This feature is intended to auto upgrade volumes when you migrate them to newer systems, in that sense it works, in the PE world it just breaks stuff)

Ok so per the chart above:

Win8.1 through Win10 v1607 *Breaks* Server 2012 ReFS by default (No ReFS on win 8 only 8.1)
Win10 v1703 *Breaks* Server 2012, Win8.1, Win10 =<1607, and Server2016 ReFS by default  <====This is where it starts to get dangerous, at 1703

So it was a small chance before but starting at 1703 its a much bigger chance of breaking something..

That is exact info.

This would be a concern if, using a WinPE 1709 with ReFS 3.3, the host volumes were upgraded.
They would become unreadable then in the host OS.

Thank you for pointing this out ChrisR.  Is a bigger concern than we thought.  Starting with 1703.  *Fixed Thanks Lancelot! :great:
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: Lancelot on October 08, 2017, 05:35:34 PM
Thanks bob.omb  :thumbsup:

updated both plugin to run Win8.1SE Win10PESE and later
DriversY\ReFS
Build\"Project Medicine"

:turtle:
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: 红毛樱木 on October 09, 2017, 01:26:14 AM
What does "Explorer.exe" need in 1709 ?
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 10, 2017, 08:33:01 AM
I tested last night ReFS, there is no worries in Win10PE.
As it is and without registry addition, Volumes with an older ReFS version are not Upgraded and keep Read and Write ability.
By cons, a ReFS 3.3 volume (windows 1709) appears in Raw, in Win10PE 15063 which support ReFS 3.2 maxi.

[attach=1]

Otherwise, I had no success with the previous registry keys for the optional creation or format ability in PE.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 10, 2017, 03:56:03 PM
I tested last night ReFS, there is no worries in Win10PE.

Otherwise, I had no success with the previous registry keys for the optional creation or format ability in PE.

Great!

Side note: ReFS formatting works perfectly fine with the registry keys provided

Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 10, 2017, 05:41:30 PM
Yes, with 15063, it works fine but I do not have ReFS proposed with 16299.15 and Format /fs:ReFS does not work

Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 10, 2017, 07:13:52 PM
Yes, with 15063, it works fine but I do not have ReFS proposed with 16299.15 and Format /fs:ReFS does not work

Are you just confirming this for regular pro edition? Or is this with [01] 07en-US x64 10.0.16299.15 Windows 10 Pro for Workstations | ProfessionalWorkstation ??

From my understanding there will be no keys needed in ProW (except to prevent auto upgrade, which you are saying may not happen) - I am converting ESD to ISO now and checking normal install's ReFS behavior for ProW...

I always want to run current releases but starting to wonder what is involved in porting 3.3 back to 1703.(Most likely not possible)  Having a USB you can boot and access drives on a dead machine is a long time feature of PE would be a shame if can't be incorporated into build for ReFS and MS puts a wall between some of us and our data...Sorry for so much ReFS in this thread it seems to be the biggest change
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: JFX on October 11, 2017, 03:20:45 AM
Seems to be all about ProductPolicy.

ProfessionalWorkstation has FileSystems-ReFs-Enabled set to 1.
Server has FileSystems-ReFs-Enabled and FileSystems-ReFsV1-Enabled set.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 11, 2017, 05:04:40 AM
Thanks JFX  :thumbsup:
UUP Enterprise x64 download is in process to catch the Enterprise ProductPolicy, with ReFs Enabled.
Maybe you already have it JFX ?
Maybe good to enable ReFsV1 too, I Don't know.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: JFX on October 11, 2017, 10:50:09 AM
Enterprise looks like ProfessionalWorkstation. Guess ReFsV1 is something deprecated.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 11, 2017, 05:54:30 PM
I tried with enterprise productpolicy in PE with FileSystems-ReFs-Enabled, ReFS is now displayed  :thumbsup:

By cons, with windows 10 enterprise or WinPE 16299.15
I am unable to create a storage space or to format with Refs 3.3
create the pool > Create storage space > Simple > Can not delete the storage space. Error 0x00000057
Format /fs:refs > Failed to Initialize State of Underlying Data Structures 112 (Gtranslate)
same with explorer or diskpart

Also, I cannot open the event log. error 50
Eventlog service is running

The same things works carefree with 15063. I do not understand what's wrong
Super! on a fresh install without any change.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: Atari800xl on October 11, 2017, 11:28:47 PM
ADK:

https://download.microsoft.com/download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/16299.15.170928-1534.rs3_release_amd64fre_ADK.iso
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 11, 2017, 11:50:44 PM
Can not delete the storage space. Error 0x00000057

For this error(PE):
Code: [Select]
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\MiniNT,AllowRefsFormatOverNonmirrorVolume,1

or

For this error(Normal):
Code: [Select]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT]
"AllowRefsFormatOverNonmirrorVolume"=dword:00000001

EDIT***

Did not notice this was the same value as before  :embarrassed:


Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: ChrisR on October 12, 2017, 07:45:53 AM
I had tried with AllowRefsFormatOverNonmirrorVolume but without more success.
In any case, on a freshly installed OS, it should work without any addition.
I re-try this morning a new win10 1709 enterprise install on VMware, I have the same result 0x00000057.
Not enough free time, I give up. ReFS is not for me.
Have you tried ReFS with 1709 Pro workstation or enterprise ?

Thanks Atari800xl for latest ADK.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 12, 2017, 09:03:16 AM
I have had no success, with ReFS on Pro for Workstations, but I have had very little time and have been making updates to my current PE build. Activation Required for ReFS? *MS_4ALL*** activates ProW then immediately rediscovers and switches version over to education (from MDL).  Hoping its just an activation issue or a problem with my source, will sort it out when I get back home later this evening. It installs fine and shows version correctly but no ReFS visible OOB on first attempt.

I did find this however: <-- For issue with Storage Spaces in VM
From web - "I had the same problem when i tested it in VmWare.
Going from 2 disks to 3 disks.
I resolved it by cleaning the 2 disks with diskpart before creating the new storagespace"

I'm sure you will have to use the above keys, but maybe cleaning with diskpart will break you through problem the rest of the way
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP and ESD - ISO to come)
Post by: bob.omb on October 15, 2017, 08:15:02 PM
Confirmed working ReFS read/write without ability to format in 1709 PE.  Supposedly product policy change allows formatting, but we are already enterprise? does proforW policy work? (I will try to figure this out)

Quote
Initial VM test = positive results. Switching from Pro to Pro Workstation instantly added ReFS format capability to diskpart. Below, I change the Product Key and you can see that diskpart instantly offers ReFS format. EDIT: Plus, I then formatted the volume as ReFS.

from bottom of page 10 below:
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update-insiderplat_pc/windows-10-fall-creators-update-to-remove-refs/6f408dc5-4663-404c-aef5-84c31f0f4dd4?auth=1 (https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update-insiderplat_pc/windows-10-fall-creators-update-to-remove-refs/6f408dc5-4663-404c-aef5-84c31f0f4dd4?auth=1)
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: Atari800xl on October 17, 2017, 12:39:14 PM
...
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: ericgl on October 19, 2017, 10:03:26 AM
So using kost's Windows Product Policy Editor, one can easily change the values in the ProductPolicy key to enable ReFS:
https://forums.mydigitallife.net/threads/windows-product-policy-editor.39411/
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: ChrisR on October 19, 2017, 03:50:10 PM
I use indeed kost's ProductPolicyEditor to build the key for PE.
But I did not add FileSystems-ReFs-Enabled in latest Win10PESE release, ReFS seems a bit tricky in 16299.15 
I can not format here, even on fresh VMWare win 10 enterprise 1709 install !
While the same work carefree with 15063.
I did not try by cleaning the disk before. But well, not top, if we need to do manipulations before using format ReFS
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: ChrisR on October 20, 2017, 01:27:56 PM
I updated the ProductPolicy with most features of Windows 10 Fall Creators Update including ReFS.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: bob.omb on October 20, 2017, 07:58:39 PM
Formatting confirmed working  :w00t: way to go ChrisR :cheers:

Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: sa mo on October 21, 2017, 07:50:56 PM
hi
this keys missing from the build:
Quote
RegHiveLoad,Tmp_Software,%RegSoftware%
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b},,Microsoft-Windows-ReFS-v1
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b},ResourceFileName,#$pSystemRoot#$p\system32\drivers\refsv1.sys
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b},MessageFileName,#$pSystemRoot#$p\system32\drivers\refsv1.sys
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b},ParameterFileName,#$pSystemRoot#$p\system32\drivers\refsv1.sys
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b}\ChannelReferences,Count,1
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b}\ChannelReferences\0,,System
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b}\ChannelReferences\0,Id,8
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{059f0f37-910e-4ff0-a7ee-ae8d49dd319b}\ChannelReferences\0,Flags,1
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018},,Microsoft-Windows-ReFS
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018},ResourceFileName,#$pSystemRoot#$p\system32\drivers\refs.sys
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018},MessageFileName,#$pSystemRoot#$p\system32\drivers\refs.sys
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018},ParameterFileName,#$pSystemRoot#$p\system32\drivers\refs.sys
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences,Count,2
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\0,,System
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\0,Id,8
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\0,Flags,1
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\1,,Microsoft-Windows-ReFS/Operational
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\1,Id,16
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{cd9c6198-bf73-4106-803b-c17d26559018}\ChannelReferences\1,Flags,0
RegHiveUnLoad,Tmp_Software
also this:
Quote
RegHiveLoad,Tmp_Software,%RegSoftware%
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..mutilityrefslibrary_31bf3856ad364e35_none_1f2d2782e2defb44,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..mutilityrefslibrary_31bf3856ad364e35_none_1f2d2782e2defb44\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..mutilityrefslibrary_31bf3856ad364e35_none_1f2d2782e2defb44\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..tilityrefsv1library_31bf3856ad364e35_none_41117573056ea59d,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..tilityrefsv1library_31bf3856ad364e35_none_41117573056ea59d\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-f..tilityrefsv1library_31bf3856ad364e35_none_41117573056ea59d\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs.resources_31bf3856ad364e35_en-us_94063be5cc1af2bf,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs.resources_31bf3856ad364e35_en-us_94063be5cc1af2bf\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs.resources_31bf3856ad364e35_en-us_94063be5cc1af2bf\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs_31bf3856ad364e35_none_ce43257ecc00c7e0,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs_31bf3856ad364e35_none_ce43257ecc00c7e0\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs_31bf3856ad364e35_none_ce43257ecc00c7e0\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refsformat_31bf3856ad364e35_none_870a01c701ba19db,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refsformat_31bf3856ad364e35_none_870a01c701ba19db\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refsformat_31bf3856ad364e35_none_870a01c701ba19db\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-fsd_31bf3856ad364e35_none_f85c6806add23570,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-fsd_31bf3856ad364e35_none_f85c6806add23570\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-fsd_31bf3856ad364e35_none_f85c6806add23570\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-mof_31bf3856ad364e35_none_f889b594adafe46b,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-mof_31bf3856ad364e35_none_f889b594adafe46b\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-mof_31bf3856ad364e35_none_f889b594adafe46b\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1.resources_31bf3856ad364e35_en-us_652586c0c57557ff,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1.resources_31bf3856ad364e35_en-us_652586c0c57557ff\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1.resources_31bf3856ad364e35_en-us_652586c0c57557ff\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1_31bf3856ad364e35_none_c49c5168f66944c4,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1_31bf3856ad364e35_none_c49c5168f66944c4\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1_31bf3856ad364e35_none_c49c5168f66944c4\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-fsd_31bf3856ad364e35_none_cf4ed9899a2a6c90,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-fsd_31bf3856ad364e35_none_cf4ed9899a2a6c90\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-fsd_31bf3856ad364e35_none_cf4ed9899a2a6c90\10.0,,10.0.15063.0
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-mof_31bf3856ad364e35_none_cf3892a19a3b633d,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-mof_31bf3856ad364e35_none_cf3892a19a3b633d\10.0,10.0.15063.0,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-refs-v1-mof_31bf3856ad364e35_none_cf3892a19a3b633d\10.0,,10.0.15063.0
RegHiveUnLoad,Tmp_Software
and this:
Quote
RegHiveLoad,Tmp_Software,%RegSoftware%
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",InstallType,1
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",ProviderType,1
RegWrite,HKLM,0x2,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",ApplicationIdentity,#$pSystemRoot#$p\system32\drivers\refs.sys
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",NameResource,100
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",ExplainResource,200
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",NeutralName,ReFS
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",InstanceType,2
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}","First Counter",7424
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}","Last Counter",7542
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",CounterCount,59
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",InstallType,1
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",ProviderType,1
RegWrite,HKLM,0x2,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}",ApplicationIdentity,#$pSystemRoot#$p\system32\drivers\refs.sys
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",NameResource,100
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",ExplainResource,200
RegWrite,HKLM,0x1,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",NeutralName,ReFS
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",InstanceType,2
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}","First Counter",7424
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}","Last Counter",7542
RegWrite,HKLM,0x4,"Tmp_Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{cb6d8ddc-a302-4349-88fd-9fcf6d3a7308}\{19b5bae2-18c5-4ab8-99de-255f0e96760a}",CounterCount,59
RegHiveUnLoad,Tmp_Software
...
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: bob.omb on October 23, 2017, 10:41:54 AM
hi
this keys missing from the build:

These keys do not appear to be needed, ReFS formatting works fine without them, and so does read write.  Formatted and moved files with PE without those keys then plugged into a normal Pro for W install and everything on the drive was working perfectly.

If there is a reason they are needed please explain why as there is no difference in my build with or without them.

Also use codebox when pasting that much in forum. (# sign at top of comment editing window)
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: sa mo on October 23, 2017, 06:09:49 PM
@ bob.omb
- i have used regseeker to take all keys with refs search and compare to the build, sincerely i am not sure if if we need all this keys ...
  any way thanks for the information  :thumbsup: , i will try to eliminate one by one...( will make search)

- for the codebox sorry didn't see it  :embarrassed:
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: Olex on October 24, 2017, 01:40:46 AM
Hi, when I build with "Logon as Admin" option on 1709 update, I cannot switch back to System account anymore. "Tscon" 1 doesn't work, it says:
"The group or resource is not in the correct state to perform the requested operation", when this is working on 1703 Creators Update.

Also "sc start tcpipreg" doesn't work, says digital signature problem, even if it doesn't have any signature in the original install.wim file.

I tried to fix these myself, but no luck for now.
Title: Re: Windows 10 1709 "RTM" build 16299.15 is out (UUP 10/03, ESD 10/05, ISO 10/17)
Post by: ChrisR on October 27, 2017, 10:18:46 AM
Late response, the days are busy currently.
I have the same for Tscon 1 but without knowing what's wrong with 1709
By cons tcpipreg service is running here