jvidal Posted October 17, 2017 Share Posted October 17, 2017 Hi! I was testing the latest version (1.5.4.12) and found a HUGE BUG. As I was adding updates to the list I noticed that about half the updates are treated as "IE Hyphenation libraries" instead of what thay really are. Also they are put under the "internet explorer" section instead of the "updates" Section. This is absolutely, totally and completely wrong! I attached a screenshot that shows the problem. I hope you guys can fix it ASAP. Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 17, 2017 Author Share Posted October 17, 2017 Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 17, 2017 Share Posted October 17, 2017 I can confirm the bug! On my PC ALL the prerequisite are listed as KB3020369 and the updates as KB971033! PN sent to legolash20! Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted October 17, 2017 Share Posted October 17, 2017 Holy mother of god. I'll try and fix that tonight. mooms and Pink_Freud 2 Quote Link to comment Share on other sites More sharing options...
AtA Posted October 19, 2017 Share Posted October 19, 2017 I can confirm this bug too! Quote Link to comment Share on other sites More sharing options...
wiktorynka Posted October 20, 2017 Share Posted October 20, 2017 I confirm the bug. Repeat the same update repeatedly. Quote Link to comment Share on other sites More sharing options...
mooms Posted October 20, 2017 Share Posted October 20, 2017 In the meantime, use 1.5.4.10. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted October 23, 2017 Share Posted October 23, 2017 Took a while to hunt it down but I managed to fix it. It was caused because a missed out adding a 'true' boolean to delete non-empty folders. Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 23, 2017 Author Share Posted October 23, 2017 Thanks a lot, Legolash!!! Quote Link to comment Share on other sites More sharing options...
sweden8 Posted October 23, 2017 Share Posted October 23, 2017 Thanks a lot. I will try it out later. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 24, 2017 Share Posted October 24, 2017 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. Quote Link to comment Share on other sites More sharing options...
sweden8 Posted October 24, 2017 Share Posted October 24, 2017 I didn´t get it to work... and this error is unknown to me. I enclose error_log.txt and Error.png error_log.txt Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 24, 2017 Share Posted October 24, 2017 For me it works. Quote Link to comment Share on other sites More sharing options...
sweden8 Posted October 24, 2017 Share Posted October 24, 2017 Its possible that I have done something wrong. I hope it shows in the errorlog. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted October 24, 2017 Share Posted October 24, 2017 I've uploaded build 16 to the test area fixing six bugs since v12. That issue was caused by me removing an option. http://wintoolkit.co.uk/Home/TestBuilds Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 24, 2017 Share Posted October 24, 2017 Just "cosmetic": WTK 1.5.4.16 shows 1.5.4.15 as version; in Changelog is 1.5.4.16. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted October 24, 2017 Share Posted October 24, 2017 Already fixed that and re-uploaded Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 25, 2017 Author Share Posted October 25, 2017 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. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 25, 2017 Share Posted October 25, 2017 Under tab "Options" at the bottom (section Debugging). But if you download the test-version 1.5.4.16 it has been corrected . Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 25, 2017 Author Share Posted October 25, 2017 i didn't see it in 1.5.4.14 either... Quote Link to comment Share on other sites More sharing options...
sweden8 Posted October 25, 2017 Share Posted October 25, 2017 1.5.4.16 works fine for me. Thank you Legolash2o Quote Link to comment Share on other sites More sharing options...
Thiersee Posted October 25, 2017 Share Posted October 25, 2017 46 minutes ago, jvidal said: i didn't see it in 1.5.4.14 either... Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 25, 2017 Author Share Posted October 25, 2017 AHhhhhhh, I was looking in THE PROGRAM'S OPTIONS!!!!!! Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 25, 2017 Author Share Posted October 25, 2017 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) Quote Link to comment Share on other sites More sharing options...
jvidal Posted October 27, 2017 Author Share Posted October 27, 2017 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)... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.