winget integration

P

puszczu

New Member
I thought winget would be preinstalled in 22H2, but its missing in latest build.
What is the best way to integrate app installer (winget) by NTLite? Do I have to download all the packages (dependencies) manually and write a script to install or there is already simpler solution? Perhaps someone can share working example?

Thanks and
Best regards
 
winget is included with DesktopAppInstaller app package, which requires UI.Xaml and both VCLibs libraries.
It's there on 21H2 and 22621 builds.
 
garlin said:
winget is included with DesktopAppInstaller app package, which requires UI.Xaml and both VCLibs libraries.
It's there on 21H2 and 22621 builds.
Click to expand...
Thanks for the heads up, will increase the importance of DesktopAppInstaller, locked behind Modern App Support, add winget info to its description.
 
garlin said:
It's there on 21H2 and 22621 builds.
Click to expand...
forgive me for my lack of knowledge and experience, but how it is there on 22621 builds?
Yesterday I downloaded and built and iso using uup dump - only pro version (22621.1.220506-1250.NI_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US).
After fresh install, I get unrecognized command error when I try to use winget in command line. I have to manually install it from MS Store before I can execute my further winget based software installation scripts.
Perhaps I'm missing something, wrong build? missing any setting or checkbox checked?
 
It's here:
C:\Users\Test\AppData\Local\Microsoft\WindowsApps\winget.exe
Actually a link to:
C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe\winget.exe

Btw garlin, can you please add winget app for simplicity to your app downloader?
 
nuhi said:
It's here:
C:\Users\Test\AppData\Local\Microsoft\WindowsApps\winget.exe
Actually a link to:
C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe\winget.exe
Click to expand...
Thank You for explanation, I will check it soon.
nuhi said:
Btw garlin, can you please add winget app for simplicity to your app downloader?
Click to expand...
I think it might be already there, I downloaded all necessary files using this app

1657277546971.png
 
puszczu said:
forgive me for my lack of knowledge and experience, but how it is there on 22621 builds?
Yesterday I downloaded and built and iso using uup dump - only pro version (22621.1.220506-1250.NI_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US).
After fresh install, I get unrecognized command error when I try to use winget in command line. I have to manually install it from MS Store before I can execute my further winget based software installation scripts.
Click to expand...

You're talking about this bug:
https://github.com/microsoft/winget-cli/issues/1793
The version of App Installer coming in the Windows 10 distribution is the original version that shipped with Windows 10. It does take time for everything to synchronize and for the store to determine an update is available. Once you have the most recent version of App Installer on the system. The Windows Package Manager is available. This also holds true for Windows 11. We are working to be a part of the original distribution for the next update to Windows 11 so the Windows Package Manager can be present before getting an updated App Installer.
Click to expand...

It sounds like by design, the ISO version of DesktopAppInstaller is incomplete and you need to integrate the Store (or GitHub) version.
 
I did more testing and it's getting really weird
I made another iso and tested on Hyper-V and here is what I got after fresh install
1. There is no such file
Code: 
C:\Users\%username%\AppData\Local\Microsoft\WindowsApps\winget.exe
nor
Code: 
C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe\winget.exe

2. There is No MS Store! its completely gone from the system, but I did not remove it by NTLite or any other way. It's just missing, I can't install any app handled by store (including desktop app installer). I can't reinstall the Store using any known solutions (by power shell or resetting...). After few hours I managed to install store by manually downloading packages with dependencies.
Perhaps it has something to do with microsoft account requirement which is present in this build, but I used unattended setup so I got legged in by local account anyway.

3. I tried installing desktop app installer manually
Code: 
powershell -nop -ep bypass -c "Add-AppxPackage -path %WINDIR%\Setup\Files\Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.appx"
powershell -nop -ep bypass -c "Add-AppxPackage -path %WINDIR%\Setup\Files\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe.appx"
powershell -nop -ep bypass -c "Add-AppxPackage -path %WINDIR%\Setup\Files\Microsoft.UI.Xaml.2.7_7.2203.17001.0_x64__8wekyb3d8bbwe.appx"
powershell -nop -ep bypass -c "Add-AppxPackage -path %WINDIR%\Setup\Files\Microsoft.DesktopAppInstaller_2022.610.123.0_neutral_~_8wekyb3d8bbwe.msixbundle"
all packages got installed without error, then winget app was available in command line, but I could not install any app because weird errors about missing sources. After adding sources manually (reset --force did not work), I still was not able to install any software because "unknown error" with random number.

Should I try different source build?
 
I use uupdump to generate script and then download files and make iso. I'm not quite sure the exact build number because I deleted all the files after generating iso, but the generated iso name is 22621.1.220506-1250.NI_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO.
I wanted to download 22H2 and excluded insider builds. I selected options to trim image only to pro version.

I will download new iso from uup and test again. I will try https://uupdump.net/download.php?id...-4c589289c0bb&pack=en-us&edition=professional (Windows 11, version 22H2 (22621.169) amd64) (according to this site, it is most recent 22H2 non insider build)
 
puszczu said:
I use uupdump to generate script and then download files and make iso. I'm not quite sure the exact build number because I deleted all the files after generating iso, but the generated iso name is 22621.1.220506-1250.NI_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO.
I wanted to download 22H2 and excluded insider builds. I selected options to trim image only to pro version.

I will download new iso from uup and test again. I will try https://uupdump.net/download.php?id...-4c589289c0bb&pack=en-us&edition=professional (Windows 11, version 22H2 (22621.169) amd64) (according to this site, it is most recent 22H2 non insider build)
Click to expand...
theres no need to download same build image again just for updates.
you can download updates manualy & integerate them to same base uup dump generated iso ie 22621.1 /////|
 
I found the reason of all issues I have been experiencing
I use a ramdisk software (32GB) to build iso images, I noticed that uupdump script uses dism to integrate updates and store apps, but dism fails when used on ramdisk (access denied error). Unfortunately script does not stop but just skips errors and continues, generating "bad" iso in the end. (bad in terms of missing component like MS Store...).

Btw, I found out that, when one extract uup downloaded zip, there is ConvertConfig.ini file, in which one can configure which store app will be integrated, by setting app level or picking up individual apps from the list
Code: 
[Store_Apps]
SkipApps     =0
AppsLevel    =0
CustomList   =0
 
puszczu said:
I use a ramdisk software (32GB) to build iso images, I noticed that uupdump script uses dism to integrate updates and store apps, but dism fails when used on ramdisk (access denied error). Unfortunately script does not stop but just skips errors and continues, generating "bad" iso in the end. (bad in terms of missing component like MS Store...).
Click to expand...

DISM depends on Windows filter drivers for filesystem calls, and probably doesn't work with RAM disks. What app did you use?
abbodi86 wrote the conversion script, and may want to fix the error handling.
 
puszczu said:
I found the reason of all issues I have been experiencing
I use a ramdisk software (32GB) to build iso images, I noticed that uupdump script uses dism to integrate updates and store apps, but dism fails when used on ramdisk (access denied error). Unfortunately script does not stop but just skips errors and continues, generating "bad" iso in the end. (bad in terms of missing component like MS Store...).

Btw, I found out that, when one extract uup downloaded zip, there is ConvertConfig.ini file, in which one can configure which store app will be integrated, by setting app level or picking up individual apps from the list
Code: 
[Store_Apps]
SkipApps     =0
AppsLevel    =0
CustomList   =0
Click to expand...
Wanting to exclude from the installation/ISO UUP also MS Edge I underline the other option of ConvertConfig.ini
[convert-UUP]
SkipEdge = 1
 
garlin said:
DISM depends on Windows filter drivers for filesystem calls, and probably doesn't work with RAM disks. What app did you use?
abbodi86 wrote the conversion script, and may want to fix the error handling.
Click to expand...
I'm using ImDisk Virtual Disk (free software). https://sourceforge.net/projects/imdisk-toolkit
It's very lightweight and simple, but perhaps there are others, more compatible software for such use

I did another test, this time downloaded iso directly from Microsoft Windows11_InsiderPreview_Client_x64_en-us_22621.iso and after NTLite session (component + tweaks + unattended) everything works fine under virtual machine. MS Store is present, winget is installed out of the box.

I also prepared another iso by uup dump, this time on non ram disk drive, and everything looks ok too, whole process took a lot longer and I saw the log of every store app being installed, so no errors this time.
 
You must log in or register to reply here.
Back
Top