RELEASE: UUPDL v0.14.42 +++FEATURE FIX RELEASE +++ Changelog v0.14.42 --fixed missing refbuilds.ini upload https://forums.mydigitallife.net/threads/uup-dump.75052/page-5#post-1368477
Don't suggest yourself by the number of files, because Microsoft changes it every build. The file you are looking for was renamed to "microsoft-windows-client-languagepack-package_nl-nl-amd64-nl-nl.esd" in 17692. API internal package database is compatible up to build 17661, you need a generated pack to be able to correctly download a newer build, so I suggest using fetchdetect (which is a complete mess by the way, but seem to work) that will create a needed pack for get script. Also if you maintain a local database, then you can use build number 0 for skip ahead, so it will check WU using latest build number you have in local database. List of files I'm getting for nl-nl AIO (39 files): Code: core_nl-nl.esd coren_nl-nl.esd microsoft-onecore-applicationmodel-sync-desktop-fod-package-amd64.cab microsoft-windows-client-desktop-required-package.esd microsoft-windows-client-desktop-required-wow64-package.esd microsoft-windows-client-features-package.esd microsoft-windows-client-features-wow64-package.esd microsoft-windows-client-languagepack-package_nl-nl-amd64-nl-nl.esd microsoft-windows-editionpack-core-package.esd microsoft-windows-editionpack-core-wow64-package.esd microsoft-windows-editionpack-professional-package.esd microsoft-windows-editionpack-professional-wow64-package.esd microsoft-windows-editionspecific-core-package.esd microsoft-windows-editionspecific-coren-package.esd microsoft-windows-editionspecific-professional-package.esd microsoft-windows-editionspecific-professional-wow64-package.esd microsoft-windows-editionspecific-professionaln-package.esd microsoft-windows-foundation-package.esd microsoft-windows-hello-face-migration-package-amd64.cab microsoft-windows-hello-face-package-amd64.cab microsoft-windows-internetexplorer-optional-package-amd64.cab microsoft-windows-languagefeatures-basic-nl-nl-package-amd64.cab microsoft-windows-languagefeatures-handwriting-nl-nl-package-amd64.cab microsoft-windows-languagefeatures-ocr-nl-nl-package-amd64.cab microsoft-windows-languagefeatures-texttospeech-nl-nl-package-amd64.cab microsoft-windows-mediaplayer-package-amd64.cab microsoft-windows-not-supported-on-ltsb-package.esd microsoft-windows-not-supported-on-ltsb-wow64-package.esd microsoft-windows-quickassist-package-amd64.cab microsoft-windows-regulatedpackages-package.esd microsoft-windows-regulatedpackages-wow64-package.esd microsoft-windows-tabletpcmath-package-amd64.cab microsoft.modernapps.client.all.esd microsoft.modernapps.client.core.esd microsoft.modernapps.client.professional.esd microsoft.modernapps.clientn.all.esd openssh-client-package-amd64.cab professional_nl-nl.esd professionaln_nl-nl.esd
Hi, I was using the miniserver till now. Today I tried the newest uup.downloader.cmd but I cannot key in numbers as USER input e.g. in CHECK FOR NEW RELEASES - NEW BUILD CHECK - CHECK FAST RING SKIP CHANNEL or in some other menus. I remember I read this long times ago how to solve this.
Iirc it was a bug in some Insider Builds regarding the new console features. Click the top left side icon on CMD Window to enter Settings, try the 'Use Legacy console' option.
17134.112 upgrades on many different systems either killed or disabled lots of things. Started last nite and until about 1:30PM today CST, i have been fixing, several Dell, HP, Acer and Alienware desktop and laptops. many programs are disabled and even when reinstalled are DEAD, so again IMO MS upgrade 17134.112 was a total F** mess. 2 systems i did a total restore back to 17134.84, then disabled WU. Business Computers that need special programs for work.
No, nothing changed. That was the reason I changed to the miniserver when it comes out, so this problem exists on my system since many builds but only in uup.downloader.cmd. sfc /scannow does not show any error. Is there a simple small test script for me? Edit: 1. a simple CHOICE /C 123 works so the choice command in the uup.downloader.cmd should work too :-( 2. I tried uup.downloader.cmd in a VM with 17134.112 and there is the same problem. What am I doing wrong in this mask CHECKING WINDOWS INSIDER FAST SKIP CHANNEL when I want to input 01 as proposed for amd64? Edit2: Sorry I misunderstood this mask CHECKING WINDOWS INSIDER FAST SKIP CHANNEL. The script shows only new releases and does not allow selecting one of these. Sorry again :-(
Start with build 17692 ,I have problem with start uup.downloader.cmd. Keep in one of the folders always and latest build make a problem to start.as pic attached. Moving out of this folder (or any other),everything is OK.
No space in folder name. Even i choose different folder...same.... Edit: If I named folder with single name is OK. Any double or more words(numbers) folder is error.
Sounds weird . The space detection isn't limitted to the folder name but to any space in the entire path, so a user name with spaces will trigger that notice if in the path. Can start the tool here perfectly from a folder with special chars and several words, separated by dots not spaces.