But CBS.LOG only for "failed due to pending updates" error... I had dedup.sys and deduppipeline.dll with wrong file hash in my pack, dunno why extraction produced different file (by only one different char inside it).
@abbodi I'm still busy, you know... one day left to update to w10 and everyone decided to do that today Anyway i confirm it installs nicely. Not yet tested against real deduped data, but I think everything should be fine now.
Are you sure it won't work? I think the issue is within the files signing, not .cab file itself since both Server and Client are now the same build, digital signature should work previous server TPs files were signed with development certificate, and don't wotk on TH2 or TH1 update.ses has nothing to do with signing, it controls the big packages deplyment (Service pack, product) i don't see errors in cbs.log and all errors in dism.log are for applicability anyway, i'll see if i can create the manual pack
Also i found some commands don't work as expected: diskpart create vdisk file="c:\vhd\windows-archive.vhd" type=expandable maximum=500000 select vdisk file="c:\vhd\windows-archive.vhd" attach vdisk format fs=ntfs quick label="Windows-Dedup-Archive" assign format and assign don't work (but can be manually done with disk management) also: powershell set-dedupschedule -name "WeeklyGarbageCollection -Enabled $false dosen't do anything it just sits and waits for input. lastly Get-DedupStatus -Volume "G:" dosen't seem to work either. but Get-DedupStatus g: does work
Yes, i saw it later not harmful i guess, no need for re-uploading the pack now will remove it when server LP are released, then the pack become MUI
So tell me, what have done to your b14393, that you can DISM it correctly? ) What edition do you have?
I unpacked update kb3176927 signed cab then repacked it, and dism accepted it normally are you sure you build is fine?
I just "your-decrypted" ESD and ISO-installed in VM(-Ware Workstation) from where I provided the screenshot of last version of your pack (with forgotten EXE)... It has to be "feature" of edition I use. I bet all those folks have another edition.
Hi, this one ran ok. Code: C:\Temp\Dedup14393>dism /online /norestart /add-package /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Processing 1 of 8 - Adding package Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [==========================100.0%==========================] Processing 2 of 8 - Adding package Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0 [==========================100.0%==========================] Processing 3 of 8 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [==========================100.0%==========================] Processing 4 of 8 - Adding package Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0 [==========================100.0%==========================] Processing 5 of 8 - Adding package Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [==========================100.0%==========================] Processing 6 of 8 - Adding package Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0 [==========================100.0%==========================] Processing 7 of 8 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [==========================100.0%==========================] Processing 8 of 8 - Adding package Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0 [==========================100.0%==========================] The operation completed successfully. C:\Temp\Dedup14393>dism /online /enable-feature /featurename:Dedup-Core /all Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. Restart Windows to complete this operation. Do you want to restart the computer now? (Y/N) n C:\Temp\Dedup14393> I will test it now.