You can want whatever you want but i think you really don't know what it takes to intercept that Temp URL. Maybe when someone who is just downloading at the time you ask, he/she can intercept the url for you.
Having a lot of trouble with this one...:/ The last three or four builds have installed perfectly, first time, secure boot on, and no problems...This one has failed three times--twice through the flight upgrade process and once through an ISO I made from the install.esd. I am in the process of trying another .esd...and will update with results... (I always upgrade--don't do "clean" installs) This build fails consistently @ 76% complete...oh, joy... Seccure boot on or off, doesn't matter. I checked Feedback and have to confess that under the filters most recent/problem/Windows installation, etc./installation, I have never seen so many reports of a build failing to install! If it doesn't work this time I'll just wait on the next build... EDIT: OK, success! First attempt with the new .esd--secure boot on. It was strange but revealing...the first ISO I made with the install.esd pulled from my drive after the first two flight upgrade attempts failed. Interesting thing was that I used a version 22 decrypter (esd-decrypter-wimlib-22.7z) on the install.esd and it appeared to create an ISO with no errors, but which failed to install. The second attempt at an iso was with an .esd I pulled from wzor's site as linked by the OP here, but when I tried to create the ISO with the same version 22 decrypter that had decrypted the install.esd--I got an error message instead, and ran the update-esd-cryptokey-data.cmd to update the decrypter with the new key--only then did it create the ISO from the second .esd. All I can think of is that the install.esd coming down through WU was being corrupted somehow--even though the two ISOs created matched in size to the byte--but only one of them, the wzor .esd with the updated cryptokey, actually installed. That would explain why the first two flight-upgrade attempts failed, as the install.esd was being corrupted every time it was being placed on my boot drive in the installation files folder. I'll do some feedback on this, no question. All's well that ends well, eh?...
I'm on 49a03, I use it to spot any Vivaldi problem. FF is not that bad lately, but still to put it on par with Opera 12 or Vivaldi needs a ton of extensions. Which makes it a not viable option for the everyday use.
The issues that I was having with Chrome thrashing my HDD and memory and then crashing are gone in this build. Made my day.
LOL by using too much memory then after filling physical memory it starts using virtual memory then the whole system slow down ( that if you have less then 8GB of memory)
Isn't that. Chrome has an incredibly stupid caching mechanism. It does huge traffic just to write the cached items. As usual the best way to deal with it is to put the cache on a ramdisk and launch it with the command --disk-cache-dir="R:\browsercache". Opera 12 did that natively more than a decade ago. But the crappy browsers we have nowadays requires more efforts.