[QUOTE = "._., Poste: 1381104, membre: 283623"] WOW! J'ai téléchargé maintenant ..... :à votre santé: Salut et merci pour l'affichage. [/ QUOTE] np !
https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-102#post-1381260 All x64 full .svf.exe all Languages added!!!
Today I installed on all my three Tablets the 1709 build. On the two 10.1" (AU101T) all was done with no problems. The problem was with the small one, 8.1" with just has 1GB RAM and 16GB ROM. The two AU101T having 2GB Ram and 32GB Rom! As all 3 running on Windows 10 Home only, Pro impossible because of missing Touch Driver for the Pro, they all should work well. Ok, the problem about on the 8.1", was because of the low space left on ROM. By the first try, I didn't get any error Message! On the second try, an Error Message came up and asked for additional 10GB of space on a USB Drive. I'd a TIF Card 64GB already attached, because I use it for to relocate incoming data to it (by settings), and that card has 38GB free, I wasn't able to use that as additional space. Unfortunately, that tablet has only 1 Micro-USB connector and I use that with a special OTG cable for charging and USB and a Mouse at the same time. First I removed the Mouse and connected a 16GB Sandisk: not worked! I then looked up for a Micro-USB Hub, 4 ports and extra Power 5V, connected that to the OTG, the Mouse and a 32GB Sandisk, fresh formatted then to the HUB and started the Tablet up and all was running. Started the Upgrade for 1709 from an ISO, downloaded from MS, and all went well with no problems. After all of that was done, I realized while working on all 3 Tablets, that MS has changed the OnScreenKeyboard to a new style and also removed the KB-Icon from the lower right System-Launch! Now I'd to place the new OSK back into Startup, still, it will not show up in the System-Launch. Anyway, that's the only minor problem I found till now! Not a big deal! I just will change the Icon for the OSK back to the old or something else, and get back to the System-Launch tomorrow! So, everything works just fine!
Oh, forget to mention, I was also installing the latest cumulative update to the new build too. the final build shows now: 16299.19
So brand new ISOs will be released for them, or the customers who bought those licenses will have to just type-in their product keys?
The blog is last Updated August 10, 2017 2:06 pm, they must have decided otherwise in the mean time, it's not on any of the currently released iso/esd's.
Meh, doesn't really matter to me anyway, but I was really interested in knowing how'd the product be delivered. Would it be like GLVK ENT keys?! That's the only interesting part for me, apart from ReFS(bootable(not present yet afaik) support.