jvidal
-
Posts
42 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by jvidal
-
-
wait, there's something wrong. The downloaded files, although called "win10 1909" contain version 18362.418 (19h1), according to the file [1].xml inside install.wim.
this doesn't add up. it should be version 18363.xxx (19h2)
edit: after installing, the about dialog says "Windows version 1909 (OS Build 18363.418)"
-
Yep, finally!
-
well,, now it's the 12th and the links for v1909 still don't work.
-
let's wait until tomorrow (12) and see if it becomes available...
-
finally. thanks!
-
but the tool offers them...see, that's what I'm talking about...
-
BTW, the links from within the tool are still giving a 404 error (even after RS5 has been -supposedly- officially released)
-
Thanks, all I'm saying is that the tool with support for the latest version should be released only after the latest version is available, otherwise you get a 404 error when trying to download...
-
Version 7.10 adds -allegedly- support for win10 1809, but it doesn't work. The links are not available. Why add support for something that has not been released yet?
-
ok. easy solution
-
Hi!
I just downloaded v1.6.0.7 and when I press the "update cache" button, the app crashes with an "major unhandled error" message and then it freezes, you have to kill the process to get outta there.
I hope this can be fixed ASAP. thanks.
-
-
I thought it might be due to a failed compilation or something that ended up with a file filled with zeroes or somethign like that.
-
if you guys noted, there was a HUGE difference in the compressed file's size.
Both exes were around 12MB (1.6.0.1 & 1.6.0.5), but v1.6.0.1 barely compressed to about 10MB, while v1.6.0.5 compressed to about 5MB. I suspect the problem lies there
-
same here, win7 x64
-
That's too bad. Thanks for replying.
c2r sucks!!!!!!!
-
Hi!
I was wondering why only the click-to-run versions can be downloaded with the tool, why no standard (MSI-based) installers?
bye!
-
I ran more tests, with Win7 X86 pro this time and ran into the infamous "could not apply the unattend.xml fromthe msu" for 7 or 8 updates.
Plus IE11 wouldn't integrate.
This behavior seems to be random, it might work one time, but fail the next.
The cumm. update wasn't integrated (but it was integrated fine with windows ThinPC)...
-
BTW, I did a quick test with 1.5.4.16 andWindows ThinPC.
I found a couple of issues:
Windows update client wasn't integrated. all three files ended up with a red "X" beside them.
(I actually don't now if this is still required or if it was replaced by a newer update)
KB3042058 and KB3172605 ended up with a "?" mark beside it (don't know what that means).
Both had the error applying the unattend.xml...
On the plus side, the big cummulative update that wasn't integrated with previous versions of WT was integrated correctly (apparently)
-
AHhhhhhh, I was looking in THE PROGRAM'S OPTIONS!!!!!!
-
i didn't see it in 1.5.4.14 either...
-
On 24-10-2017 at 6:11 AM, Thiersee said:
Liam forgot in both the new releases 1.5.4.13 (official) and 1.5.4.14 (Test) a debug-box checked; therefore starting WTK executes only a test on the boot.wim.
Go into "Options" and uncheck the option "Boot.wim Test".
Then works WTK as usual.
Where is that "boot.wim test" option?
I don't see it anywhere.
-
Thanks a lot, Legolash!!!
-
Windows 10 October 2019 download links broken
in Windows ISO Downloader
Posted · Edited by jvidal
yeah, after installing I noticed that I had the correct build (1909 build 18363.418). I also read somewhere that 1903 updates also apply to 1909, is that right?
Edit: It seems they do. I updated from 18363.418 to 18363.449 using KB4522355