Well Need to find out which one, may be it will be MiniNT only. Then you said people need to reboot to Enable/Disable MiniNT mode. well a reboot is not necessary instead just importing the registry setting is enough. To Enable ReFS MiniNT Mode. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT] "AllowRefsFormatOverNonmirrorVolume"=dword:00000001 To Disable ReFS MiniNT Mode. Code: Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT] This will instant enable/disable DISM /Online operation without any reboot.
Update : Using ReFS MiniNT Mode also breaks the USB Safely Remove Options. still have to look what's breaking the installation of os when the ReFS registry is integrated to wim. This is Regarding about the Data Deduplication feature pack, is there any order in which we should install this package cab files or can we install in any order. Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" also you have said to enable this feature "Dedup-Core /All" apart from this I found out there is one more feature "File-Services-Search-Service" which is in disabled state when the Deduplication pack is integrated to the wim. I think this feature will be useful for windows search
Hello, yes, this pack uses files actual after W8-1-1 (U1). But seems, I didn't tested it properly :/ Please test the integration again, but AFTER: Code: DISM /image:C:\mount /Add-Package /PackagePath:C:\MSU_1st Dism /Commit-Image /MountDir:C:\mount DISM /image:C:\mount /Add-Package /PackagePath:C:\MSU_2nd Dism /Commit-Image /MountDir:C:\mount Please put these (U1) KB updates in MSU_2nd: Code: x3_AMD64-all-windows8.1-kb2919355-x64_e6f4da4d33564419065a7370865faacf9b40ff72.msu x4_AMD64-all-windows8.1-kb2932046-x64_6aee5fda6e2a6729d1fbae6eac08693acd70d985.msu x5_AMD64-all-windows8.1-kb2938439-x64_3ed1574369e36b11f37af41aa3a875a115a3eac1.msu x6_AMD64-all-windows8.1-kb2937592-x64_4abc0a39c9e500c0fbe9c41282169c92315cafc2.msu And these (U1) to MSU_1st: (All remaining KB updates you wish to add and those needed as requirements for U1) And at the end of the list: Code: x1_AMD64-all-windows8.1-kb2919442-x64_f97d8290d9d75d96f163095c4cb05e1b9f6986e0.msu x2_AMD64-all-windows8.1-kb2939087-x64_89d4949cd698c645c7a6e96a012eecab44d5c5e1.msu Then try to do: Code: dism /online /add-package /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab /packagepath:Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab /packagepath:Package_595_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18.cab /packagepath:Package_206_for_KB2887595~31bf3856ad364e35~amd64~~6.3.2.0.cab dism /online /enable-feature /featurename:Dedup-Core /all
I had used the Windows 8.1 Prov VL GA may be that's why it gave an error, will try with the Windows 8.1 Update1 and see what happens..
Just found: Deduplication is autoupdated by Windows Update or by commands like: Code: DISM /image:C:\mount /Add-Package /PackagePath:C:\MSU ...so in fact those update packs aren't required... Just integrating Deduplication, then integrating MSU updates and then online downloading of regular WU offers is sufficient.
Big update of the pack and many components. (Everything is now compatible with W8-1-1.) v2-5 Use Total Commander's folder synchronization feature against previous version v2-0 to see, what is new.
When integrating Fraunhofer MP3 Professional pack for Windows 7 and using the Advanced or Both Advanced & Professional Codec Registry Settings the Setup gives error But When using Professional Codec Registry Settings the Setup works properly.. This doesn't happens with Windows 8.x but only with Windows 7
Hi, I am trying to import the registry key from Windows To Go Feature but I get an error: Not all data was successfully written to teh registry. Some keys are open by the system or you have insufficent privileges to perform this operation...I disabled the UAC, I opened Registry Editior via PSTools but the same error. Suggestions ? Thanks ! Windows 8.1 x64
The ACM files are there only for backup (in WindowsDefaultFiles.rar), do NOT copy them to your OS, as they are already provided by MS with OS, just run proper REG file. You should also navigate to the following reg-keys (before registering): (listed for x64 OS - in x32 OS there is no Wow6432Node branch) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 ...and clean ANY reference for l3codeca.acm. After this is done (PRO or BOTH Method) registry files should be imported to register l3codecp.acm. In BOTH-Method l3codeca.acm uses different identifier "msacm.l3codec" then it does on the original untouched OS "msacm.l3acm", because "msacm.l3acm" is used by l3codecp.acm after reg-import. So cleaning step is needed. (It can be done by registry file, which will delete the original l3codeca.acm values - but I didn't made it.) BTW: Advanced Codec is limited, so sufficient is: l3codec_pro_xXX.reg l3codec_both_xXX.reg is some sort of my obsession. With it you will have two codecs registered: 1st without any limits and 2nd with encoding limits as displayed below on the VirtualDub pictures:
So split the regfile to sections and import them one of the another, so you can see, which section generates the error... BTW: The only important part of the REG file is the "namespace" one (below) + the sections containg 8E0C279D-0BD1-43C3-9EBD-31C3DC5B8A77 ID, which adds new icon to Control Panel, other classes things aren't important... Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{8E0C279D-0BD1-43C3-9EBD-31C3DC5B8A77}] @="Portable Workspace Creator" So basically if you have added new icon to Control Panel successfully, you can omit the rest...
Moderate I've been playing with DeDup on win8.1 Unfortunately, the 9600 build version wants to update itself on windows update. Obviously I can simply ignore it, but trying it anyway results in an extremely slow primary drive. I'm trying to figure out how to make a package update thing, but I admit I'm a bit lost. It would help if things weren't labeled 1313_package_for_2919355 or whatever in the servicing directory... Do you have any ideas on how I can perhaps find updated files from server2012r2 and port them over? Maybe some sort of hard disk monitoring software when using the enable-feature command or something? It's way over my head since I don't usually work with these feature files...
There are only 3 three updates of Deduplication feature since RTM version 9600.16384: KB2887595 (Package_206) "Microsoft-Windows-Dedup-Filter" version="6.3.9600.16399" "Microsoft-Windows-Dedup-Pipeline" version="6.3.9600.16399" "Microsoft-Windows-Dedup-Service" version="6.3.9600.16399" KB2883200 (Package_595) "Microsoft-Windows-Dedup-Filter" version="6.3.9600.16425" KB2919355 (Package_3760) (same as applied two above) "Microsoft-Windows-Dedup-Filter" version="6.3.9600.16425" "Microsoft-Windows-Dedup-Pipeline" version="6.3.9600.16399" "Microsoft-Windows-Dedup-Service" version="6.3.9600.16399" I've played with it and the best way to pre-create fully updated Deduplication feature is to build ISO including these steps: Code: DISM /Mount-Wim /WimFile:C:\ISO\sources\install.wim /index:1 /MountDir:C:\mount dism /image:C:\mount /add-package /packagepath:"C:\CAB\Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab" /packagepath:"C:\CAB\Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab" dism /image:C:\mount /enable-feature /featurename:Dedup-Core /all DISM /image:C:\mount /Add-Package /PackagePath:C:\MSU Dism /unmount-WIM /MountDir:C:\mount /Commit ...where MSU dir will contain: windows8.1-kb2919355-x64_e6f4da4d33564419065a7370865faacf9b40ff72.msu ...and where CAB dir will contain: Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab ...it will 1st integrate Deduplication and then update it with latest files from KB2919355. So obviously you will need KB2919355 EVEN when you play with ISO with already integrated KB2919355. Another way is to install the updates like: Code: dism /image:C:\mount /add-package /packagepath:"C:\CAB\Package_206_for_KB2887595~31bf3856ad364e35~amd64~~6.3.2.0.cab" /packagepath:"C:\CAB\Package_595_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18.cab" (I have build Package_206_for_KB2887595~31bf3856ad364e35~amd64~~6.3.2.0.cab and Package_595_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18.cab myself and placed them in Deduplication pack. Same as that Package_3760_for_KB2919355... .cab could be built.) ...but with this method, DISM checks if the updates required for KB2883200 and KB2887595 are installed too, so you can receive DISM error.