We build systems with Windows 10 v1607 LTSB IoT Enterprise on them and the Unified Write Filter applied to the C: drive
The following write filter exclusion is applied: file add-exclusion C:\Windows\System32\spp\store
The product key is installed during an UnAttend step that occurs BEFORE the write filter is enabled:
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>MyComputerName</ComputerName>
<ProductKey>MyProductKey</ProductKey>
</component>
The write filter is enabled as the last step and the system is reboot a final time.
At this point, we try to activate windows. We do this:
slmgr /ato <-- This returns activation success
reboot
slmgr /dli <-- This returns "notification" (i.e. no longer activated)
The only way we can get this to work is to activate windows with the write filter disabled!!
We also found we have to run BOTH of the above commands with the write filter disabled or the activation won't persist.
This process (to activate with the write filter enabled) worked with Windows 8 Standard Embedded but no longer works now (with Windows 10 v1607).
Is there a different set of write filter exclusions we need now? How do we fix this?!
