I'll be back later to reply to a few posts in this thread. However, they can't change the fact that the OS files should (will) be the same, which can always be installed using an older (current) version of update.exe, or even manually. The Embedded restrictions are entirely artificial! So the most they could do is make the installation checks harder or require something besides POSReady, etc. In conclusion, of course the updates are identical, and should (will) continue to be, because there's NO reason for them to be different. value in a typical location to control behavior.) Well, now I finally know. simple key from another update instead of a new reg. Note: Its update.inf DOES check for a ProductSuite of EmbeddedNT!Īnyway (unrelated to Embedded), I discovered that update is needed! (Or at least the usual registry key(s) that indicate Installed.) The updated win32k.sys from a separate, corresponding update back then actually checks if the HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2686509 key exists, which is extremely weird! (e.g. no files or special registry entries), which I really noticed after checking. All that file does is check some stuff before allowing the update (NOT that file) to "install." I say "install" because I never installed it as it doesn't seem to do anything (e.g. I already saw elsewhere that the Embedded update contains kblChecker E.dll instead of kblChecker.dll. Then the one from (#21), 12-034 (KB2686509), keyboard layout vulnerability. Again, this is really a SP2 vs SP3 difference. WMP 9 code is basically the same, effectivelyġ0-082 (KB2378111) - WMP 10-11 identical WMP 9 Embedded wmp.dll version older/smaller (4.51 vs 4.66 MB). They both appear to ONLY be for SP2 (see update.inf SP req.), so SP3 would be shared with "normal" XP. After the next win32k.sys update they were again identical. Then we have 10-048 (KB2160329) for win32k.sys where the Embedded version is a day or two and 1 version older (.6002 vs. These SP3 updates were not identical and had different times, so I disassembled them and it's only the internal timestamp and checksum that differ, but the code is identical: These SP3 updates are identical between "normal" and Embedded: And the SP3 files in those "interim" Embedded updates are. ALL other updates before and after (except one oddball.) are shared because they're the SAME. The simple summary? The ONLY reason those separate updates exist for Embedded is to support installation on SP2 (after "normal" updates became SP3-only). 2010 - what's significant about that? That's between when support ended for "normal" XP SP2 (July 2010) and Embedded XP SP2 (Jan. If you search the Update Catalog for "XP Embedded," you'll see that prior to May, there are only 21 updates for XP Embedded. Why? Because there has never, ever been any difference between the "normal" and Embedded XP updates! I now present the results of my complete and thorough investigation. ![]() These are 100% legit and complete updates. Most importantly, the response/warning from Microsoft is 100% lies! (99.99% at least if you want to cut them some slack for future possibilities.) Absolutely disgusting statements: "Significant risk of functionality issues?" Umm, NO, nothing should (will) change in the future. ![]() After doing a happy dance, I had to investigate more myself, especially after seeing issues alluded to here and doubts about the updates' validity. I guess I had really been out of the loop (had hardly checked Wilders last couple months) since I just accidentally saw a Google result mentioning this trick about 10 days ago. You will need to use Internet Explorer for that.This is really good stuff guys! So great to have further updates to allow XP to die off more "naturally" over the next years instead of being left more vulnerable and hoping other solutions can cover us. That should take you to the Windows Update website which should either walk you through the process of updating whatever needs to be updated, or first install some software on your machine that will allow it to analyze your machine and then walk you through the steps required to update that machine. You should be able to, in Internet Explorer, visit. Windows XP, I actually don’t see any reason not to go all the way to Internet I strongly suggest that you update to, at least, Internet Explorer 7. It is not secure it is not being updated. Two things here: One is nobody should be using Internet Explorer version 6Īnymore. Unsupported browser versions, even in old operating systems. Answercast #11, I look at the security implications of using IE 6 and other
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |