[INFO - DISCUSSION + Downloads] Windows 10 1809 FINAL b 17763.xxx (PC) [RS5]

Discussion in 'Windows 10' started by Enthousiast, Sep 18, 2018.

Tags:
Page 297 of 357
  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5921 Enthousiast, Dec 19, 2019 (OP)
    What language and architecture you want?
     
  2. achernov

    achernov MDL Novice

    Mar 28, 2017
    43
    19
    0
    #5922 achernov, Dec 19, 2019
  3. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5923 utilitasetveritas, Dec 19, 2019
    English and 64 bit.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5924 Enthousiast, Dec 19, 2019 (OP)
    Nope, not needed anymore when using the updates from the overview.
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5925 Enthousiast, Dec 19, 2019 (OP)
  6. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5926 utilitasetveritas, Dec 19, 2019
    Sorry. I want the LTSC.
    OK. I am downloading an ISO now. Is there anything else I should do to it before using it on a PC?
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5927 Enthousiast, Dec 19, 2019 (OP)
    Let me ask you a question, on what grounds did you decide, you want to install a specific SKU like Enterprise LTSC?
     
  8. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5928 utilitasetveritas, Dec 19, 2019
    A... SKU... don't know what is that :)
    Anyway, I want the Enteprise version because it doesnt have bloatware.
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5929 Enthousiast, Dec 19, 2019 (OP)
    You mean, "i want the Enterprise LTSC version"?
     
  10. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5930 utilitasetveritas, Dec 19, 2019
    Yes. Enterprise LTSC.
     
  11. qwesta

    qwesta MDL Senior Member

    Jul 22, 2011
    345
    133
    10
    #5931 qwesta, Dec 19, 2019
    Wow, why didn't you say that from the beginning then?
     
  12. Wannabe

    Wannabe MDL Junior Member

    Aug 1, 2007
    72
    58
    0
    #5932 Wannabe, Dec 19, 2019
    To @utilitasetveritas defense, the first message posted was about getting LTSC, but then changed to Enterprise back to LTSC back to Enterprise and finally back to LTSC again...
     
  13. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5933 utilitasetveritas, Dec 20, 2019
    I dont understand. You are saying that there are other version of Windows that can also be LTSC?
    There is a non-LTSC Enteprise edition?
    I thought that the Enteprise version is only LTSC.
     
  14. MK_1981

    MK_1981 MDL Novice

    Jul 13, 2017
    27
    9
    0
    #5934 MK_1981, Dec 20, 2019
    there is AFAIK:

    home
    pro
    ENT
    ENT N
    ENT LTSC
    ENT LTSC N

    and I believe EDUCATION, that I don't know nothing about.
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5935 Enthousiast, Dec 20, 2019 (OP)
    These are all Consumer and business SKUs:
    https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-296#post-1566240
    Consumer:
    Code:
    [01] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Home | Core
[02] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Home N | CoreN
[03] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Home Single Language | CoreSingleLanguage
[04] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Education | Education
[05] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Education N | EducationN
[06] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro | Professional
[07] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro N | ProfessionalN
[08] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro Education | ProfessionalEducation
[09] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro Education N | ProfessionalEducationN
[10] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro for Workstations | ProfessionalWorkstation
[11] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro N for Workstations | ProfessionalWorkstationN
    Business:
    Code:
    [01] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Education | Education
[02] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Education N | EducationN
[03] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Enterprise | Enterprise
[04] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Enterprise N | EnterpriseN
[05] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro | Professional
[06] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro N | ProfessionalN
[07] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro Education | ProfessionalEducation
[08] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro Education N | ProfessionalEducationN
[09] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro for Workstations | ProfessionalWorkstation
[10] 12/5/2019 en-US x86 10.0.17763.914 Windows 10 Pro N for Workstations | ProfessionalWorkstationN
    Enterprise 2019 LTSC (the full name) is a specific SKU based on normal Enterprise but with the long term servicing channel, 5+5years of support and no bi-annual feature updates (new builds), like the normal non LTSC SKUs get.
    It doesn't have Cortana or Edge and no Store (+no UWP apps).

    Enterprise 2019 LTSC is released in 3 builds, all info can be found here:
    https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631
     
  16. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5936 utilitasetveritas, Dec 20, 2019
    OK. I will look at the links. Thank you.
     
  17. utilitasetveritas

    utilitasetveritas MDL Novice

    Aug 4, 2015
    11
    1
    0
    #5937 utilitasetveritas, Dec 21, 2019
    OK. It took me some time, but I managed to do it. I thank you all for your help.
     
  18. MaveRick23

    MaveRick23 MDL Member

    Apr 13, 2013
    229
    15
    10
    #5938 MaveRick23, Dec 25, 2019
    what is differences and which one should i install:

    1. SSU;
    2. CU;
    3. DU;?


    Thanks for your update man.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,306
    450
    #5939 Enthousiast, Dec 25, 2019 (OP)
    Use W10UI for smart automation of updates integration.

    Manualy it's SSU > CU.

    DU for sources is just extract the cab, and put the files in "ISO:\sources" folder.
    DU for safeOS is not needed when the CU is being integrated.
     
  20. achernov

    achernov MDL Novice

    Mar 28, 2017
    43
    19
    0
    #5940 achernov, Dec 25, 2019
    Last edited: Dec 25, 2019
    I tried integrating the latest updates to my 2019 LTSC (17763.1) 64bit image with W10UI_7.5
    Screenshot_3.png

    The integration completed but it gave this errors
    Screenshot_1.png
    Screenshot_2.png

    Here is the DISM log:
    Code:
    2019-12-25 17:05:38, Info                  DISM   PID=7140 TID=3036 Scratch directory set to 'C:\Users\Admin\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-12-25 17:05:38, Info                  DISM   PID=7140 TID=3036 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
2019-12-25 17:05:38, Info                  DISM   PID=7140 TID=3036 Scratch directory set to 'D:\W10UItemp_30232'. - CDISMManager::put_ScratchDir
2019-12-25 17:05:38, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:38, Info                  DISM   PID=7140 TID=3036 Successfully loaded the ImageSession at "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM" - CDISMManager::LoadLocalImageSession
2019-12-25 17:05:38, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-12-25 17:05:38, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:38, Info                  DISM   DISM Manager: PID=7140 TID=3036 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-12-25 17:05:38, Info                  DISM   DISM.EXE:
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2019-12-25 17:05:38, Info                  DISM   DISM.EXE:
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=x86, Number of processors=4
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17763.1
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /English /ScratchDir:"D:\W10UItemp_30232" /Export-Image /SourceImageFile:sources\boot.wim /SourceIndex:1 /DestinationImageFile:temp.wim
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:38, Warning               DISM   DISM Provider Store: PID=7140 TID=3036 Failed to load the provider: C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2019-12-25 17:05:38, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE:
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2019-12-25 17:05:53, Info                  DISM   DISM.EXE:
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=7140 TID=3036 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:53, Info                  DISM   PID=10216 TID=1840 Scratch directory set to 'C:\Users\Admin\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-12-25 17:05:53, Info                  DISM   PID=10216 TID=1840 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
2019-12-25 17:05:53, Info                  DISM   PID=10216 TID=1840 Scratch directory set to 'D:\W10UItemp_30232'. - CDISMManager::put_ScratchDir
2019-12-25 17:05:53, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:53, Info                  DISM   PID=10216 TID=1840 Successfully loaded the ImageSession at "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM" - CDISMManager::LoadLocalImageSession
2019-12-25 17:05:53, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-12-25 17:05:53, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2019-12-25 17:05:53, Info                  DISM   DISM Manager: PID=10216 TID=1840 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-12-25 17:05:53, Info                  DISM   DISM.EXE:
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2019-12-25 17:05:53, Info                  DISM   DISM.EXE:
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=x86, Number of processors=4
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17763.1
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /English /ScratchDir:"D:\W10UItemp_30232" /Export-Image /SourceImageFile:sources\boot.wim /SourceIndex:2 /DestinationImageFile:temp.wim
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Connecting to the provider located at C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-12-25 17:05:53, Warning               DISM   DISM Provider Store: PID=10216 TID=1840 Failed to load the provider: C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2019-12-25 17:05:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2019-12-25 17:05:54, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2019-12-25 17:05:54, Info                  DISM   DISM.EXE:
2019-12-25 17:05:54, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2019-12-25 17:05:54, Info                  DISM   DISM.EXE:
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-12-25 17:05:54, Info                  DISM   DISM Provider Store: PID=10216 TID=1840 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    Did I do something wrong or can I still use the updated image? The windows I used was win10 32 bit, does it matter if I use it to integrate updates on a 64bit image?
     
Page 297 of 357