Posted August 6, 201212 yr Something is wrong with the first logon installer (WinToolkit Installer 4.6.3, ultimate sp1 x64). It's the first time I've encontered an issue with the directx installer - it told me it was corrupt??? I'm using it for more than a year with absolutely no problems. You can find it here...I checked the size of the one from the USB stick ''disk'' and the one on my hdd - they're the same, so the ''corrupt'' case is out of the question. Or maybe win toolkit did something to it when adding it to the apps folder? Please investigate this one Lego, it's too much for me.
August 6, 201212 yr Same MD5 checksum? I haven't changed a thing to do with silent installers in a long time.
August 6, 201212 yr Author Actually... no. That is the thing I found to be very weird... D4C2A66762BDA854D81C17B8707BB09E for the one on the usb stick ''iso'' (apps generated folder), and 6FE0757387C593C823F51D8C4C0FA1A8 for the one on the hdd.But the size seems to be exactly the same...
August 6, 201212 yr It probably got corrupted then, i remember last week i think it was that i fixed an issue with copying file? when was it that you added the directx silent installer?Just manually replace the file on the USB with the known working one without running WinToolkit.
August 6, 201212 yr Author tonight, I played with various builds to investigate that 0x67 bsod. I think I used v52 test 1 when I integrated this one, or v51 test 21 (?). I'm not sure, I deleted the earlier builds. Currently I'm only integrating updates, so I can't invstigate this one now.
August 7, 201212 yr Just tried this and the MD5 files match. Where was the extracted DVD when you added the DirectX silent? HDD, Network, USB?Did you manually copy and paste the files onto the USB stick after?
August 7, 201212 yr Author The extracted dvd was on my hdd. I made from it an iso on the same partition of the hdd with win toolkit. And afterwards copied the files from the mounted iso to the usb stick. So no mistakes on my end... I think Edited August 7, 201212 yr by RicaNeaga
August 7, 201212 yr It might have been a one off when copying to the usb stick, either way i'll check my code.Just replace the file on the USB with a working one, you don't have to re-run WinToolkit.UPDATE: I have just fixed a bug when copying folders but it's not related to your issue.
August 7, 201212 yr Author Ok, I'll try it again with build 54 and afterwards I'll check the md5. And of course I'll report back
_14e30a.png)
_8126ce.png)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.