Does anyone here have a handle on WinSxS (Windows Side-by-Side)? Remember back when we were patching and replacing user32.dll.mui? We had to ensure every last copy of it was replaced, a couple of which were down winsxs paths. So likewise, why is it that every last copy of tcpip.sys needn't be replaced? You'll notice in v2.2 of the patch (unlike v2.1), the winsxs areas are not updated. Sure, the files have long, weird names, but they're still tcpip.sys. Per the comment link I posted just above, the patch seems to work, or at least appeared to work for one person, but is this a problem waiting to happen (e.g. if you had to run "SFC /scannow")? Is it really not necessary to update all copies?
What do you mean? That's why he's using ReadyDriver+, to sidestep the F8 thingy. Some consider that easier than going the test signing route.
Was your boot problem with Yaron anything more than the F8 requirement? I participate frequently in the comments thread on the patched drivers (see my previous link) and very rarely did I see an issue not explained by that (or software firewalls blocking the new tcpip.sys). It works well, and you know exactly what it is, as it's been proven since the very beginning (you can examine the patched file with an editor or even patch your own, but that's not needed). I don't have any experience with CrackTcpip.sys, since I was uncomfortable with a 3rd-party black box being introduced. Based on what you're saying, however, it needs an update and shouldn't be used going forward until then. Should you overwrite tcpip.sys version 6.0.6001.18063 with tcpip.sys version 6.0.6001.18000? I would say definitely not. It would be better to never install KB 952709 in the first place if you needed to do that. It is an extremely minor update for only a handful of specific things. 3b): ReadyDriver+ is merely a mod to Vista's boot manager. It's not a resident program. It essentially automates the F8 for you and that's it. Otherwise, you have to do it manually starting with SP1--unless you go through the tcpip.sys test signing process (see above), but that's for another post. Note: If you dual-boot, ReadyDriver+ apparently makes that more difficult (see post above), but I have no experience with that scenario. 3c): It really is just extracting all files to a temp directory and then running the appropriate batch. It's all automated from there, except for ReadyDriver+, which you're given the choice to install or not at the end of the process.
You can use the yaron fix, and then uninstall readydriver, and test sign the new tcpip.sys file, and then remove the test mode watermark.
QUESTION: If I uninstall KB952709, will the tcpip.sys version back to old version? Since I think this is the best as I can update later once cracktcpip.sys has been released. Some more I'm not really used to "taking ownership" method. A bit complicated, which I think if uninstalling KB952709 works, would prefer this method.
Hello bjf2000, to answer your first question: in fact, I have never tried the solution of Yaronmaor, so I cannot say anything to boot problems. ==> 3c) OK, thx, I understand. So in my case, I would only have to install "InstallPatch32-18063.bat" and "SetupReadyDriverPlus.exe", that´s all. Question 1 Would deinstalling KB 952709 change the tcpip.sys from 6.0.6001.18063 to 6.0.6001.18000? What is your opinion? Should i try to do so? I am doing WU manually, and then everytime de-selecting install of KB 952709? Question 2 I have only Vista in my system, I am not dual booting with another OS. If I understand things correctly: After installing "SetupReadyDriverPlus.exe", the boot process of Vista will be as normal? Or do I have to do something manually? Thx and wish you a nice day.
Hi m8, I'm using the Yaronmaor solution with the ReadyDriver+ thing and it's working great with Vista Ultimate 32 bit. The F8 proccess is completly automated (if you are not using dual boot). Don't worry, just execut the batch file and follow the instructions. I think this is the best solution. Anymore error 4226...
Oh..... although using Yaronmaor´s solution, you have event id 4226? Or did you mean: "not anymore error 4226"?