1. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Need to check with NTLite updates folder structure and also as I have read the NTLite uses some special method to integrate some updates which can't be integrated in a regular way.

    The ToolKit auto-selects the WHD updates based on the menu chosen for Windows 7

    Windows 7 with SP2 aka Convenience Pack
    Windows 7 without SP2 aka Convenience Pack

    I need to update this feature to match the latest WHD repository.

     
  2. gample

    gample MDL Novice

    Jan 6, 2019
    1
    0
    0
    Hello, I was able to install the Microsoft Store through MSMG ToolKit on Windows Server 2019, but I can not download the app through the Microsoft Store. In addition, the Microsoft.Services.Store.Engagement file does not appear in the installation window.
    How do I the install Appx file?
     
  3. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    783
    629
    30
    Can I ask why do you do not convert the WIM file to ESD? This reduces the size significantly for me.
     
  4. gilbert1a

    gilbert1a MDL Novice

    Nov 25, 2018
    25
    30
    0
    While install.wim does not reach the critical value of 4 GB, it does not make sense, because the speed of working with a WIM file is much higher than with ESD. In my opinion, the use of ESD is justified only in terms of saving space on bootable media or when install.wim becomes more than 4 GB.
     
  5. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    783
    629
    30
    Sometimes, particularly with x64 images, I have found that the WIM can exceed the 4GB limit. So, out of habit, I now convert my WIM files to ESD.

    I haven't tried WIM files for some time, so I will test these soon to see what sizes I get.
     
  6. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    783
    629
    30
    Tested only with x86 image due to time constraints.

    WIM file was 2.56GB and took about 4:55 to reach the Cortana OOBE screen.
    ESD file was 2.18GB and took about 4:43 to reach the Cortana OOBE screen.

    I agree building the ESD file takes about an extra 10-15 minutes. But I feel the size reduction alone is worth it.
     
  7. gilbert1a

    gilbert1a MDL Novice

    Nov 25, 2018
    25
    30
    0
    Thank you very much for the test. The time difference was not very big. Most likely you have a more modern computer. I often have to maintain obsolete computers at work, where the difference in installation time between wim and esd reaches 50-60%.
     
  8. Krager

    Krager MDL Senior Member

    Jan 9, 2017
    396
    233
    10
    #9369 Krager, Jan 11, 2019
    Last edited: Jan 11, 2019
    Thanks for the help guys, I'll mess with it some more. I don't ~have~ to do the component cleanup, just would like to get it working in case I need it to reduce the size of the image, that cleanup takes a long time to run. This stuff is pretty involved and can be confusing at times, kind of puts me in my place.
     
  9. hoxlund

    hoxlund MDL Member

    Nov 6, 2017
    112
    54
    10
    Also ESD files are just encrypted WIM. See why using ESD file doesn't work? It's encrypted.
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,679
    103,529
    450
    #9371 Enthousiast, Jan 11, 2019
    Last edited: Jan 11, 2019
    ESD is not the same as install.esd;)

    And ESD's are not encrypted since 15063 (iirc) was released.

    Compressing install.wim to install.esd saves approx. 30-33% in file size.
     
  11. THUMPer1

    THUMPer1 MDL Junior Member

    Mar 8, 2011
    68
    9
    0
    The weirdest thing is going on.
    My sticky notes crashes all the time. If I remove it from the image and install it through the store, it will crash. If I leave it in the image, and remove other random apps it will stay installed but crash. Does anyone know if sticky notes is dependent on anything
    else?? Here is event viewer crash info.


    Faulting application name: Microsoft.Notes.exe, version: 3.1.46.0, time stamp: 0x5bec8d97
    Faulting module name: KERNELBASE.dll, version: 10.0.17763.134, time stamp: 0x1659a33b
    Exception code: 0xe06d7363
    Fault offset: 0x0000000000055299
    Faulting process id: 0x2460
    Faulting application start time: 0x01d4a9ec26ebf23e
    Faulting application path: C:\Program Files\WindowsApps\Microsoft.MicrosoftStickyNotes_3.1.46.0_x64__8wekyb3d8bbwe\Microsoft.Notes.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 078bb991-2484-4285-bdc8-2564bf778ca7
    Faulting package full name: Microsoft.MicrosoftStickyNotes_3.1.46.0_x64__8wekyb3d8bbwe
    Faulting package-relative application ID: App
     
  12. Krager

    Krager MDL Senior Member

    Jan 9, 2017
    396
    233
    10
    Got rid of the "file not found" problem with component cleanup, but now I'm getting some weirdness. When component cleanup runs the second time (after component removal) it only runs to twenty percent then says it completed successfully. Makes no difference in the size of the final image whether I run component cleanup a second time or not. Output below;
    Code:
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Image Version: 10.0.17763.253
    
    [===========                20.0%                          ]
    The operation completed successfully.
    
    One note, I'm not using the /ResetBase switch because I found it doesn't make much difference in the final size of the image and it disables the Reset Windows feature.

    Script below for ref;

    Code:
    dism /mount-wim /wimfile:d:\temp\install.wim /index:1 /mountdir:d:\temp\wim_offline
    dism /image:d:\temp\wim_offline /add-driver /driver:d:\home\comp\software\win10\build\drivers /recurse
    dism /image:d:\temp\wim_offline /add-package /packagepath:d:\home\comp\software\win10\updates\kb4470788_serv_stack_12-05-18_1809-x64.msu
    dism /image:d:\temp\wim_offline /add-package /packagepath:d:\home\comp\software\win10\updates\kb4480116_cumulative_01-08-19_1809-x64.msu
    dism /image:d:\temp\wim_offline /cleanup-image /startcomponentcleanup
    
    toolkithelper d:\temp\wim_offline AADBrokerPlugin
    toolkithelper d:\temp\wim_offline AssignedAccessLockApp
    toolkithelper d:\temp\wim_offline BioEnrollment
    toolkithelper d:\temp\wim_offline ContentDeliveryManager
    toolkithelper d:\temp\wim_offline Cortana
    toolkithelper d:\temp\wim_offline EdgeDevToolsClient
    toolkithelper d:\temp\wim_offline LockApp
    toolkithelper d:\temp\wim_offline MapControl
    toolkithelper d:\temp\wim_offline ParentalControls
    toolkithelper d:\temp\wim_offline PeopleExperienceHost
    toolkithelper d:\temp\wim_offline QuickAssist
    toolkithelper d:\temp\wim_offline RetailDemoContent
    toolkithelper d:\temp\wim_offline SettingSync
    toolkithelper d:\temp\wim_offline SkypeORTC
    toolkithelper d:\temp\wim_offline SmartScreen
    toolkithelper d:\temp\wim_offline WindowsDefender
    toolkithelper d:\temp\wim_offline WindowsMixedReality
    toolkithelper d:\temp\wim_offline WindowsReaderPDF
    toolkithelper d:\temp\wim_offline XboxApp
    toolkithelper d:\temp\wim_offline XboxGameCallableUI
    
    toolkithelper d:\temp\wim_offline AdobeFlashForWindows
    toolkithelper d:\temp\wim_offline AssignedAccess
    toolkithelper d:\temp\wim_offline CEIP_SQM
    toolkithelper d:\temp\wim_offline DeviceLockdown
    toolkithelper d:\temp\wim_offline EaseOfAccessThemes
    toolkithelper d:\temp\wim_offline FirstLogonAnimation
    toolkithelper d:\temp\wim_offline HomeGroup
    ::toolkithelper d:\temp\wim_offline InternetExplorer
    toolkithelper d:\temp\wim_offline KernelDebugging
    toolkithelper d:\temp\wim_offline MultiPointConnector
    toolkithelper d:\temp\wim_offline RemoteAssistance
    toolkithelper d:\temp\wim_offline SnippingTool
    toolkithelper d:\temp\wim_offline UnifiedTelemetryClient
    toolkithelper d:\temp\wim_offline WindowsErrorReporting
    toolkithelper d:\temp\wim_offline WindowsPhotoViewer
    toolkithelper d:\temp\wim_offline WindowsSubsystemForLinux
    toolkithelper d:\temp\wim_offline WindowsToGo
    toolkithelper d:\temp\wim_offline WinSAT
    
    dism /image:d:\temp\wim_offline /cleanup-image /startcomponentcleanup
    dism /image:d:\temp\wim_offline /enable-feature /featurename:netfx3 /source:e:\sources\sxs
    dism /unmount-wim /mountdir:d:\temp\wim_offline /commit
    
     
  13. THUMPer1

    THUMPer1 MDL Junior Member

    Mar 8, 2011
    68
    9
    0
    I have the same issue.
     
  14. sonnet

    sonnet MDL Novice

    Aug 23, 2007
    10
    0
    0
    I've tried version 9.1 with RS4 image and when I select option 4 (Remove), it doesn't show me options to remove stuff but rather gives me the same options I'd get if I press 5.
    Anyone elese get this issue?
    I wasn't getting this issue with version 8.8
     
  15. AsaadSoft

    AsaadSoft MDL Addicted

    Jul 29, 2015
    542
    171
    30
    after installing the OS, is it necessery to run

    DISM / Online / Cleanup-Image / StartComponentCleanup / ResetBase
    ??

    what does this command do ? and why should one run it ?
    what if one didn't ??
     
  16. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Microsoft.Services.Store.Engagement is a dependency pack required for SolitaireCollection but not for Store.

    The ToolKit installs these dependency files by default for all components along with AdverstingXaml, VC Framework and VC Runtimes

    Right now I have tested with Client editions only, need to check for Server.

     
  17. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Yes it will take time if there are updates integrated.

     
  18. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    StickyNotes requires Store App to function and In the current version I have put a check to retain the shared files if the store is removed.

    Will again test the feature.

     
  19. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    That's normal to show 20% when you are doing the cleanup for the second time.

    Using /ResetBase will not completely remove the superseded components for that you need to use the below tweak which will breaks the Reset PC function.

    Code:
    Reg add "HKLM\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Configuration" /v "DisableResetbase" /t REG_DWORD /d "0"