1. akq

    akq MDL Novice

    Jul 5, 2015
    48
    12
    0
  2. AeonX

    AeonX MDL Addicted

    May 24, 2013
    796
    725
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    3,262
    1,733
    120
    @xinso -- I tried your regedit for Enabling Edge in EnterpriseS. I started out with original image. Installed. Installed update that the new one for .576 needs. Restarted. Took ownership of packages in registry, and merged your regedit. Verified visually successful. Restarted. Updated to .576. Successful. Installed both Edge packages. Restarted. Still Edge opens, then shuts immediately. :( Any suggestions?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    762
    556
    30
    Change your order. I believe it has to be:

    1. Install Edge
    2. Apply reg fix
    3. Update.

    then it has to work.

    Cheers.
     
  5. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    3,262
    1,733
    120
    #905 dhjohns, Dec 17, 2016
    Last edited: Dec 17, 2016
    Thanks. I will try that. Is this the order to do OFFLINE also?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    762
    556
    30
    I haven't tested it yet, but it should be like that for both.
    The CU has to be tricked into asuming that it is a W10 pro version and thus updates the Edge components.

    Cheers.
     
  7. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    3,262
    1,733
    120
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. akq

    akq MDL Novice

    Jul 5, 2015
    48
    12
    0
  9. coromonadalix

    coromonadalix MDL Senior Member

    Jul 21, 2009
    440
    87
    10
    I've played with WinToolkit it does its job but you have to find "your solutions" ... played with the version 2 still in development,

    I'm trying to make some kind of batch command in MSMG without breaking the original code to do this :

    Choice #4 option 1 remove A G H I J K L N Q S T U X Y Z 1

    Choice #4 option 3 and yes remove B C D E F J K M N P Q

    I don know if its possible to do multiple selection in CMD files ??? thats what MSMG misses, i hope the GUI version will do this ? I have seen some kind of batch command with install wim tweak with a timed pause between commands, but now cant find it :(

    Keep the good work
     
  10. AeonX

    AeonX MDL Addicted

    May 24, 2013
    796
    725
    30
    #911 AeonX, Dec 17, 2016
    Last edited: Dec 17, 2016
    I've never used WinToolkit to export images so I was not aware of this behavior.

    You can use the MSMG Toolkit to export images also by going to Tools > WIM Manager > Export (it asks if you want to create another WIM file, choose yes or it will add another index to the existing image).

    I have verified that just exporting index 2 after deleting the old install.wim and renaming the new WIM file to install.wim and then deleting the NanoServer folder from the installation media will be enough to reduce the ISO size to fit on a DVD without needing remove the files in C:\Windows\WinSxS\Backup
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. AeonX

    AeonX MDL Addicted

    May 24, 2013
    796
    725
    30
    The goal was to make it easier to remove the files in C:\Windows\WinSxS\Backup because removing them manually results in permission errors to delete the files. But I have checked that this is not necessary to reduce the ISO size so it is possible to use only the MSMG Toolkit :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,669
    103,497
    450
    Last time i've tried that i discovered it results in corrupted system files after installing the windows image.

    But i read back and i only see people removing all sorts of windows components but are discussing how to simply delete/export/rebuild an index....
     
  13. AeonX

    AeonX MDL Addicted

    May 24, 2013
    796
    725
    30
    A while ago I thought about doing this but I saw some comments in the forum that made me conclude that these files may be needed. I do not remember exactly why but it made me give up the idea. After all, there is very little space that is gained I think is not worth the risk.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,702
    14,431
    340
    #915 xinso, Dec 18, 2016
    Last edited: Dec 18, 2016
    Step1: Install Edge
    Step2: Import registry trick as TrustedInstaller
    Step3: Install CU

    That'd been tested with last CU. I'll test .576 and feedback.
     
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,702
    14,431
    340
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,669
    103,497
    450
    #917 Enthousiast, Dec 18, 2016
    Last edited by a moderator: Apr 20, 2017
    These are the errors when you use the cleanup manager of WTK:

    Code:
    2016-12-18 10:56:01, Info                  CSI    000001df [SR] Cannot verify component files for WCF-System.IO.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:02, Info                  CSI    000001e1 [SR] Verify complete
    2016-12-18 10:56:02, Info                  CSI    000001e2 [SR] Verifying 100 (0x00000064) components
    2016-12-18 10:56:02, Info                  CSI    000001e3 [SR] Beginning Verify and Repair transaction
    2016-12-18 10:56:03, Info                  CSI    000001e5 [SR] Verify complete
    2016-12-18 10:56:03, Info                  CSI    000001e6 [SR] Verifying 100 (0x00000064) components
    2016-12-18 10:56:03, Info                  CSI    000001e7 [SR] Beginning Verify and Repair transaction
    2016-12-18 10:56:03, Info                  CSI    000001e9 [SR] Verify complete
    2016-12-18 10:56:03, Info                  CSI    000001ea [SR] Verifying 100 (0x00000064) components
    2016-12-18 10:56:03, Info                  CSI    000001eb [SR] Beginning Verify and Repair transaction
    2016-12-18 10:56:05, Info                  CSI    000001ed [SR] Verify complete
    2016-12-18 10:56:05, Info                  CSI    000001ee [SR] Verifying 41 (0x00000029) components
    2016-12-18 10:56:05, Info                  CSI    000001ef [SR] Beginning Verify and Repair transaction
    2016-12-18 10:56:06, Info                  CSI    000001f1 [SR] Verify complete
    2016-12-18 10:56:06, Info                  CSI    000001f2 [SR] Repairing 6 components
    2016-12-18 10:56:06, Info                  CSI    000001f3 [SR] Beginning Verify and Repair transaction
    2016-12-18 10:56:06, Info                  CSI    000001f4 [SR] Cannot verify component files for System.IO.Log.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-us", VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001f5 [SR] Cannot verify component files for System.IO.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001f6 [SR] Cannot verify component files for Microsoft-Windows-DIMS.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001f7 [SR] Cannot verify component files for Microsoft-Windows-DIMS-AutoEnroll.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001f8 [SR] Cannot verify component files for Microsoft-Windows-DIMS-KeyRoam.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001f9 [SR] Cannot verify component files for WCF-System.IO.Log, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
    2016-12-18 10:56:06, Info                  CSI    000001fb [SR] Repair complete
    2016-12-18 10:56:06, Info                  CSI    000001fc [SR] Committing transaction
    2016-12-18 10:56:06, Info                  CSI    00000200 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    
     
  17. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    3,262
    1,733
    120
    #918 dhjohns, Dec 18, 2016
    Last edited by a moderator: Apr 20, 2017
    This is specific for where I have MSMG Toolkit installed, but it is working with .576.
    Code:
    @Echo Off
    cd %systemroot%\system32
    call :IsAdmin
    reg load HKLM\test C:\Portable_Files\3-Toolkits\ToolKit-v6.1\Mount\Install\windows\system32\config\software
    setacl.exe -on "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" -ot reg -actn setowner -ownr "n:Administrators"
    setacl.exe -on "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" -ot reg -actn ace -ace "n:Administrators;p:full"
    Reg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallClient" /t REG_SZ /d "DISM Package Manager Provider" /fReg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallName" /t REG_SZ /d "Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0.mum" /f
    Reg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallLocation" /t REG_SZ /d "\\?\d:\rs1.bin.amd64fre.dep\mergedcomponents\images\client\packages\\" /fReg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "CurrentState" /t REG_DWORD /d "112" /f
    Reg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "SelfUpdate" /t REG_DWORD /d "0" /fReg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "Visibility" /t REG_DWORD /d "1" /fReg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallTimeHigh" /t REG_DWORD /d "30531506" /f
    Reg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallTimeLow" /t REG_DWORD /d "76431985" /f
    Reg.exe add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.14393.0" /v "InstallUser" /t REG_SZ /d "S-1-5-18" /fpause
    reg unload HKLM\test
    pause
    Exit
    :IsAdmin
    Reg.exe query "HKU\S-1-5-19\Environment"
    If Not %ERRORLEVEL% EQU 0 (
     Cls & Echo You must have administrator rights to continue ... 
     Pause & Exit
    )
    Clsgoto:eof
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,702
    14,431
    340
    #919 xinso, Dec 19, 2016
    Last edited: Dec 19, 2016
    Yes, Windows10.0-KB3206632-x64-14393.576.1.8 still needs the trick - if not been applied before.
     
  19. AeonX

    AeonX MDL Addicted

    May 24, 2013
    796
    725
    30
    #920 AeonX, Dec 19, 2016
    Last edited by a moderator: Apr 20, 2017
    Thank you. Modifications in Windows\WinSxS often cause headaches unless you know what you are doing.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...