Jump to content

w2k4eva

Member
  • Posts

    64
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United States

Posts posted by w2k4eva

  1. 1 hour ago, Mathwiz said:

    Useless. What about 360Chrome? Well, I briefly see the correct page - but it quickly reverts to the same useless crap above. Even with Chrome, the Wayback Machine lets me down!

    Attempting to go back to an earlier version, August & Sept. 2019 just return captured 404 pages, and May 19-28 just lock up the browser - and now I've lost the cursor here on MSFN! I never realized the Wayback Machine could screw up a Web browser so badly.

    The harder I try the worse it gets! I lost all my opened tabs on the last browser restart!

    Could someone please explain the magical secret to actually viewing this archived Web page?

    I've been seeing this Wayback problem for at least 4 years now. It seems to affect many (most/all?) MS KB pages that were crawled from 2016 onward.

    1 hour ago, mina7601 said:

    When it showed the correct page (on Chrome), I clicked Stop on the address bar, and I was able to view the web page fully without any issue.

    I never had much luck with this method, since for me the page load takes several seconds after clicking Stop to take effect. So I must stop it before the page is shown and it was very hard to get the timing right on something I can't see yet and am not sure exactly how long it will take on any given attempt.

    What I did notice is that over the years MS has changed the format of URLs for their KB pages, and usually the older version of the URLs was from a time before this wayback problem. So fortunately for this particular update there is actually an older crawl with the different format of URL that works, even from SeaMonkey 2.49.2 on XP:

    http://web.archive.org/web/20150602151315/https://support.microsoft.com/en-us/kb/898461

    (notice the /en-us/kb/ part, these are usually the better formatted crawls)

    Sadly for other updates there isn't always an older crawl that will work, and sometimes I am stuck with having to view page source and poke through the HTML tags to find the unformatted content (which is generally still present although not rendered correctly/at all).

     

    • Like 3
  2. On 12/8/2021 at 3:42 PM, Mcinwwl said:

    Do we have a list of SSE2-only XP updates? or does this comment solve it all?

    There are a few lists, depending on whether you do/don't use MS Office, .NET, WMP11, IE8 etc.

    Some posts:

    https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1156088

    https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1162280  (and next post too)

    https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1167061

    On 12/8/2021 at 3:42 PM, Mcinwwl said:

    I Ran XP updates bundles on my 2001 machine with Athnlon 4, non SSE2 and I think I might have broken the system this way, as some features work... and others do not.

    Perhaps you want the opposite list, of updates that are SSE2-free?

    https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/?do=findComment&comment=1162417

  3. I'm wondering if this will change WU into a DRM?

    No. I have this update installed on at least 3 systems - two of which have had the HDDs replaced several times so Windows got reinstalled and updates re-applied several times - and have never seen any issues from it.

    18 hours ago, DbLH3liX said:

    It's interesting that when I reboot, I'm offered 94 updates via the systray popup but if I close it, the WU shield will still sit in the systray this time with only the above update being offered. After reading about each update offered on reboot, on the next reboot I chose around 40 of them to be installed and all appeared to be going well however the only one that was going to be installed was again this same KB898461. So I cancelled it.

    Continuing to quote from the same KB article as luweitest found above,

    Quote

    The files for the Package Installer for Windows are installed in the following folder:

    %windir%\System32\PreInstall\WinSE\WXP_%lcid%_v1

    Note The placeholder %windir% represents the location of the Windows system directory. The placeholder %lcid% represents the language identifier for the operating system that the computer is running. For more information about language identifiers, visit the following Microsoft Web site:

    http://msdn.microsoft.com/en-us/library/ms776324.aspx

    The following files are installed in this folder:

    Update.exe.ref

    Updspapi.dll.ref

    Spuninst.exe.ref

    Spcustom.dll.ref

    Spmsg.dll.ref

    Spupdsvc.exe.ref

    You can look there to see if you have any of these files.  Depending on which updates you have already installed, you may have some of them (minus the .ref suffix) also in \windows\system32 or elsewhere, probably even a newer version.

    In any case updates downloaded from the Update Catalog will generally have these files (or more likely a newer version, this set is VERY old, from 2005) packed inside each update as needed, although there is the occasional poor quality update that has a missing file, these will probably have been flagged somewhere in this massive thread. (As noted above, "Downloads from the Windows Update Catalog site are not affected.") So you could just get ALL your updates from the catalog and install them manually without needing to install this one first.

    I suspect Windows Update considers this to be a prerequisite for doing any further updates, this may be why you see this behavior of not doing the other updates. If you want WU to install ANYTHING for you, this one is probably needed first.

    But beyond that, I'm a little surprised WU did anything at all, I thought the update server was no longer compatible with XP since they changed all the certificate signatures to SHA2 only....

    • Upvote 1
  4. 17 hours ago, DbLH3liX said:

    It's been soooo long since I even had WU turned on that I don't know how to get it to stop offering me that particular update - other than install which I see now is not the best option.

    You could (assuming you have "custom" mode selected rather than Express mode) highlight it and then look for the "hide" link to click. But choosing to download them manually from the catalog and install only after researching each one is the safer option.

  5. 21 hours ago, erpdude8 said:

    it could be just a glitch with the MS update catalog server

    It's a pretty persistent glitch, I've been seeing this for more than a week now. And yes, on wired ethernet, not even wifi. In some cases, repeating the page load does not produce the links even after 10 or more reloads.

    At least the suggestion to use the googlebot UA does seem to work nicely for the catalog site. Too bad it has the opposite effect for thehotfixshare.net and some other sites - it will cause a not-so-nice forbidden error there.

    FWIW, my normal UA would be Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 SeaMonkey/2.49.2

    Edit - I have also been seeing (intermittentently) incomplete data from the catalog. Sometimes a search comes up with nothing found, other times it will find some items but have others missing - such as listing only 14 items when there are actually 17 to be returned. This is both for search results, and also for the replacement info when one of these search items is clicked. Sometimes all replacement items are missing entirely, other times only a subset is returned when I already know certain items should be there but are not.

  6. Well, the fixed IP address turned out to be the relevant clue. I changed this back to automatic assignment from the router's DHCP service, rebooted, and had no connection. Investigating this showed the XP DHCP client service had somehow gotten disabled. Resetting this to Automatic solved the issue.  Apparently Comodo likes to see the DHCP handshake happening for whatever reason, even if it does not actually need the IP address - I can even go back to fixed IP address now without getting that 90 minute delay any more!

    • Upvote 1
  7. On 6/20/2019 at 8:53 AM, medowe said:

    I'm holding KB4494528, KB4493563, KB4501226 because of reported issues.  What should I do with them & how do I install them?

    For KB4494528 do the regsvr thing like Ed_Sln and others have said.

    I installed KB4493563 and do not see any problem, but I am using the US English version in case that matters.

    KB4501226 is a time zone update (these are usually neither critical to have, nor troublesome if you do use it)  for Morocco and the Palestinian Authority. I installed it with no problems.

  8. 6 hours ago, Usher said:

    There is NO ntdll.dll file in KB4493563 downloaded from Microsoft Update Catalog. Update installer contains only ole2.dll and patches for other files

    Did you end up with a corrupt download? Or are you using a non-ENU version? I got this from the catalog on 18 Apr 2019 and it does indeed contain ntdll.dll version 5.1.2600.7682. I even re-downloaded it again a few minutes ago from the catalog and the file is identical to the April download.

    I do agree though that the English version of ntdll.dll has the last error message duplicated and the other message missing as you describe.

  9. Has nobody else ever seen this?

    I ran scans with MBAM, SuperAntiSpyware, and Avast boot time scan. As expected, no malware found.

    Also noted another odd thing. The 90 minute delay can be cut short by temporarily disabling the ethernet adapter; the GUI unlocks, and the tray icon works again. Re-enable it, and everything is good to go. FWIW, I found it was set up for a fixed IP address rather than the usual assignment from the router's DHCP server, so it wasn't even waiting for an IP address.

    Any debugging suggestions?

  10. Is anyone else here using an old version of Comodo? (3.14.130099.587 for me, or possibly some of the v5 series)

    I've had this version installed (just FW and Defense+, not the AV, for that I use Avast 6) on this machine and running perfectly for more than 4.5 years. But around 4/29 it started behaving oddly (on just this one system, I have it running perfectly on several others). That's when I noticed that the system tray icon allows calling up the GUI for a little while immediately after booting, but somewhere between 2 and 3 minutes post boot, the tray icon goes unresponsive. When this happens I also cannot call up the GUI from the start menu, nor from desktop shortcut. Then after roughly 90 minutes, suddenly the GUI that would not start earlier finally appears and thereafter works as if nothing were ever wrong. This delay seems pretty consistent as does the 2-3 minutes postboot, almost as if something has a timeout, though I don't know what it is waiting for.

    I checked in Task Manager during this time, and there are no unfamiliar processes listed. Both cmdagent.exe (the service portion) and cfp.exe (the GUI portion) are running as expected, but I can't switch to cfp.exe during this 90+ minutes. Trying to kill cfp.exe during this time simply hangs Task Manager. Leaving this sit for the 90+ minutes will let it suddenly unlock and everything goes back to normal. It isn't a normal sort of network issue, I can surf and check email just fine during this time, the only thing I cannot do is open the Comodo GUI.

    I tried looking with the process list tool in an old version of Spybot; this has the added bonus of showing what network connections a process has open, which I can't check in the Comodo UI since I can't get to that while it is hung. It seems to have one ephemeral port open, the port number changes every few seconds while the GUI is not responding, but these changing ports will suddenly stop and the open port vanishes when the GUI becomes available again.

    Checking system event logs gives no clues, likewise Comodo's own logs show nothing odd. I even tried setting a rule on Comodo to log its own traffic but there are no entries from that rule. Other rules do make log entries during this time so it isn't a logging issue.

    Searching the Comodo forums finds several posts with similar symptoms (all from version 3.x or 5.x, I didn't see any later) but all of the supposed cures end up not solving it even for the posters who initially thought they had found the answer. (Apart from "upgrade your OS, then update to latest version", generally something post-ver 5 - but then why did this version work perfectly for 4.5 years on this system and even longer on my other systems?) I have tried the uninstall-reboot twice-reinstall path a couple times with initial success, but the problem always returns after 2-3 reboots so it isn't really the solution.

    I plan to run more malware scans later today but so far have not found anything; since there are no other symptoms I'm not really expecting to find anything when they are finished.

    Assuming the scans come up clean, does anybody have a suggestion for how I might track down the cause of this odd behavior?

     

  11. 9 hours ago, Dave-H said:
    9 hours ago, glnz said:

    So this new XP update.  There are two flavors -

    Security Update for Windows XP SP3 (KB4500331) - Windows XP
    and
    2019-05 Security Update for WES09 and POSReady 2009 for x86-based Systems (KB4500331) - Windows XP Embedded

    Which one am I now?  Through Nov 2014 I was XP.  Since then I've been a cash register.

    What's your guidance?

    I suspect they're the same thing, I downloaded the two files, and they are only 4 bytes different in size!

    The "payload" stuff is indeed the same. What is different is the catalog file, because it is signing the files branches.inf and update_SP3QFE.inf. These inf files contain slightly different timestamps between the versions. The other interesting difference is that the update_SP3QFE.inf file for the plain-XP version does not have the Prerequisite section that is present in the posready version; that section is what restricts the update from being applied to plain XP.

    Since that section is missing from the plain version, wouldn't those who did the reghack be able to use either version without modifications?

    • Like 1
  12. On 11/10/2018 at 4:08 AM, tomasz86 said:

    For a text editor, I use MiXplorer which is a simple but advanced file manager with text / code editing functionality. It is not available on the Play Store though, so you would have to download it either from XDA or other source like APKMirror. It is also not open source, but I have not been able to find any viable alternative to it. The text editors available on F-Droid are either extremely barebone and/or buggy, and the ones on the Play Store are ridden with ads.

    I mostly just use the editor included inside Ghost Commander.  It's pretty basic but serves my needs. Ghost Commander is ad-free, tracker-free and open source. It's also root-aware, though it will work for unrooted devices too for as much access as filesystem permissions allow. There's even older versions in case your android is very old, I use ver 1.54.1b2 on my old FroYo device (this old version is supposedly compatible all the way back to 1.6 Donut), current version is for 2.3.3 Gingerbread & up.

    On 11/10/2018 at 4:08 AM, tomasz86 said:

    I personally try to use open source apps whenever possible and/or also lightweight apps. As such, the majority of them come from F-Droid, directly from GitHub / GitLab, and from the Play Store or other sources only if there is no alternative. While it is not always the case, the vast majority of the open source apps are free and also ad-free.

    Second this! If I can't find something open source, I do make sure to check the IzzyOnDroid app lists to see how snoop-y it is likely to be or if there are alternatives I haven't considered yet. He does list which problematic libraries are compiled into what apps and if trackers are (not) found in them (look for the gold star icon).  For instance, Office Suites and Text Editors lists a lot of editors you might check into. Another bonus to open source apps is they are more likely to still be compatible with older devices.

    A great open source non-google app is Yalp Store. This is a must for androids too old to install the current play store app like my FroYo device (it supposedly works back to 2.0 Eclair), and has active development (a new version was released in response to a bug I posted last fall).

    For email there is either K9 (for newer androids) or Squeaky (for older androids), both open source from the same codebase.

    I love CSipSimple for VoIP calling/texting over WiFi, it used to be on both playstore and f-droid (see https://f-droid.org/wiki/page/com.csipsimple) but has gone missing since I found it there. One last location survives, http://web.archive.org/web/20180816022955/http://nightlies.csipsimple.com/stable/ which does have the last version.

    It's none of Google's business where I hike or drive, so Navit gives an alternative to the preinstalled GPS/map apps. You can pre-download whatever maps/databases you like from several sources (including OpenStreetMaps, or you can make your own) and there is no need for a map server/user tracking/ad serving/whatever. The version on f-droid is older than the playstore version. The UI is rather goofy and takes a bit of getting used to so reading the wiki is a big help. Despite this I found it well worth the time I spent figuring out how to use the app and even extend it a little to show my favorite locations (there are forum posts on how to do this).

    There is an android section on http://software.oldversion.com/android/ in case you want an older version that is no longer on the playstore, though this is not an open source repo.

  13. 3 hours ago, Mathwiz said:

    I'm not following you, or at least, it's not working here.

    When I click on that URL it goes directly to the "This hotfix is no longer available" page for KB4343220. There's no EULA to accept. Clicking the URL again just brings up the "This hotfix is no longer available" page again.

    Same here. Even worse, this problem exists for ALL hotfixes, even ones I already downloaded. Even if you already know the actual DL link, in a form like http://hotfixv4.microsoft.com/Windows Server 2003/sp3/Fix200653/3790/free/315139_ENU_i386_zip.exe from having downloaded it before, the same thing happens. Seems that the DNS entry for hotfixv4.microsoft.com now has a new CNAME pointing to hotfixv4.trafficmanager.net, not sure when that happened.

  14. 6 hours ago, marv said:

    If I dont integrate kb2698365, then kb4489973 integrates fine. But kb2698365 updates also other files.

    MS12-045 KB2698365 was for MDAC 2.8SP1, I seem to recall that for W2K builds this did not always integrate well with other MDAC updates, though I was not using nlite. I wouldn't be surprised if a similar issue exist with the XP version too. Are you able to integrate just this one by itself? If so perhaps close the nlite session, then start a second session for kb4489973? There may be a post by tomasz86 or bristols on the W2K and/or hotstream board about this...

  15. On 1/31/2019 at 3:38 AM, luweitest said:

    The symptom is caused by C:\Documents and Settings\<account>\NTUSER.DAT and C:\Documents and Settings\<account>\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat do not have access permission for corresponding service account. I located those 4 files and set them to inherit the permission from parents, restart, and problem solved.

    I had initially tried adjusting permissions on just those 4 files. It reduced, but did not completely eliminate the event log errors for my system. For me the problem did not completely resolve until I also adjusted the rest of the folders as indicated. YMMV.

  16. 23 hours ago, wyxchari said:

    regedit.exe     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\NoDriveTypeAutorun     0xFF

    Do you connect your system to a domain controller? If so does the setting revert after you disconnect from the domain controller? I assume you have installed KB967715 and KB971029?

    Finding the relevant details in the pile of MS documentation can be problematic. But KB967715 has this to say:

    Quote

    Note This setting appears in both the Computer Configuration and User Configuration folders. If the settings conflict, the setting in Computer Configuration takes precedence over the setting in User Configuration.

    So you may need to change the key you are setting to be

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\NoDriveTypeAutorun     0xFF

     and I can't figure out why MS has so many articles describing use of the wrong key!

    There is also the

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\HonorAutorunSetting    0x01

    that is described later in the same article.

    You might need to repeat the steps in https://www.bleepingcomputer.com/forums/t/437944/how-to-disable-autorun/#entry2556075 for each USB stick you own, kinda tedious, and what about new sticks you do not yet own or haven't gotten around to adjusting settings for?

    So much for the MS way. A more interesting approach is at

    https://www.esecurityplanet.com/views/article.php/3848951/Two-Approaches-to-Securing-Autorun-and-AutoPlay-in-Windows.htm

    • Upvote 1
  17. On 12/6/2018 at 8:01 AM, liamZ said:

    Hi, anybody knows if there is a hotfix for the file volsnap.sys?, (mine is dated 2008-14-4 and version 5.1.2600.5512)

    This is the problem I have: On Windows 7 I use Previous versions, and every time I plug my USB hard drive on my Windows XP and after that I plug it on my Windows 7 I loose all the snapshots of this drive, with this error: volsnap event ID 29: The shadow copies of volume F: were aborted during detection.

    That original version is the only one I know of.

    FWIW, dencorso's linked KB article is still available from MS at http://support.microsoft.com/kb/926185

    On 12/6/2018 at 2:59 PM, liamZ said:

    I think there is no solution for my case, cause the solution they offer is to disable the volume in Windows XP so it can not delete the shadow copies.

    In my case I want to access my USB drive from Windows 7 and Windows XP. That's why I hoped there were some hotfix for this issue and a new version of volsnap.sys.

    That USB drive, are you using it for backups from a backup type program, or is it something you use to make manual copies with? Do you write to it from both W7 and XP, or only from W7 and just do reads from XP?

    If XP usage is going to be read-only, you could try setting the volume mount for the USB drive in XP to be read-only rather than the default read-write mount. IIRC there was a regedit or something to make this change, I don't have it handy right now but maybe someone else remembers it? That might keep XP from destroying the W7 shadow copies there.

    You might want to change the settings for System Restore in both XP and W7 to not monitor that USB drive, maybe even delete the restore points stored on it (if any), at least that should avoid creating new ones that would corrupt the shadow copies.

    Another possibility is to tell W7 to store the shadow copies for the USB drive elsewhere, like maybe on the W7 system drive (hopefully XP will not have access to that so can't delete them). See https://ccm.net/faq/2679-how-to-turn-off-volume-shadow-copy#how-to-edit-the-disk-space-allocated-to-shadow-copy for instructions.

    Do you also use Previous Versions on XP? I think it did not come by default (at least on Home) but have seen some people claim it can be installed there, from https://www.microsoft.com/en-us/download/details.aspx?id=16220. While XP does have a copy of vssadmin.exe, it is older than the W7 version and I'm not clear if it is able to do the same thing and move its snapshots of the USB drive to the XP system drive (where hopefully W7 will not delete them), but if it is able you could try that too.

    I don't know whether installing the volume shadow service SDK on XP would help or not, but it is available at https://www.microsoft.com/en-us/download/details.aspx?id=23490 if you want to check that out.

    On 12/6/2018 at 2:59 PM, liamZ said:

    I tried to disable the driver volsnap.sys but I get a BSOD. 

    You probably don't want to disable the driver for volsnap.sys since it would be needed by the shadow copy service that runs by default. If you want to stop the service itself there are also instructions for that a bit earlier in the above ccm.net link, this should be the same for both XP and W7. In that case you might also want to turn off the Microsoft Software Shadow Copy Provider service, similar method but different name. Both of these services can be typically called by backup programs including MS Backup and also System Restore so if you use those this might not be a good idea. More info about these services is at http://www.blackviper.com/windows-services/volume-shadow-copy/ and http://www.blackviper.com/windows-services/microsoft-software-shadow-copy-provider/ .

    On 12/6/2018 at 2:59 PM, liamZ said:

    Anyway I don't know why they didn't fix this with an update for volsnap.sys for Windows XP when Vista came out in 2006, cause this could lead to an important data loss.

    Back in 2006 https://blogs.technet.microsoft.com/filecab/2006/07/14/how-restore-points-and-other-recovery-features-in-windows-vista-are-affected-when-you-dual-boot-with-windows-xp said:

    Why this fix is not trivial for Windows XP: Backporting volsnap.sys to Windows XP would require significant development and testing time. The entire Volume Shadowcopy Service (VSS) subsystem in Windows Server 2003, Windows Vista, and Windows Server “Longhorn” would need to be backported to Windows XP and would likely break a number of third-party backup applications that rely on the current version of volsnap.sys in Windows XP.

    for whatever THAT may be worth.

  18. For the file itself, you could visit https://support.microsoft.com/en-us/help/975599/stop-error-when-you-put-a-computer-that-is-running-windows-7-or-window then look near the top of the page for the link text "Hotfix Download Available", click that; there will be a page where you can mark the checkbox for the version you want (x86), then give an email address. The site will then email you a download link to click. When you have the download you can use 7-zip or similar to extract the file.

    As for the custom installer, you would have to ask Dibya, you could try sending him a PM.

    • Upvote 1
  19. I still haven't figured out where my files came from but turned up some possible MS sources for yours (apart from 3rd party stuff like cellphone packages, tablet packages, GPS packages, etc) .

    At https://ryanvm.net/forum/viewtopic.php?t=9200 there is some discussion and mention of KB971286. The KB article still exists and mentions the relevant files/versions but the package (WINUSB_UPDATE_XP-SRV03.exe) has been pulled from the update catalog, it is not on wayback, and apparently nobody posted it to thehotfixshare either. In the last post of the thread there are non-MS download links.

    It also gave me a lead to KB970159 which at one time was thought to be a prerequisite. Again the KB article still exists but the package (Microsoft Kernel-Mode Driver Framework Install-v1.9-Win2k-WinXP-Win2k3.exe) has been pulled from the update catalog.

    On https://msfn.org/board/topic/175487-standalone-winusb-installer-for-xp-kb971286/ cdob points out the android sdk which has a link to latest_usb_driver_windows.zip where he describes getting the winusb package out of the winusbcoinstaller2.dll. What he doesn't mention is that alongside this the zip also has wdfcoinstaller01009.dll, and packaged inside that is the kernel mode framework package that went missing from KB970159.

    Also in this thread blackwingcat mentioned kb975559 which MS intended for W7 but it contains a newer winusb.sys 6.1.7600.16421 and Dibya says he uses it in his custom installer. This too has the KB article still available but the package is not in the update catalog. At least for this one there is a hotfix download available, though it is intended for W7 so it might not install to XP from this package even if the file inside could work (this may be why Dibya did his custom installer for it).

     

  20. My \Windows\System32 folder has a winusb.dll, size 24136 bytes created/modified 02 Nov 2006 7:00:10AM, version 6.0.6000.16386, with valid MS signature. This is the only version of this file that I have anywhere on the system, no second copy in dllcache, drivers, any of the windows update uninstall folders, etc. I can't find any reference to such a file in my notes about updates that I added so I'm guessing it came preinstalled, I don't know exactly what it does. The properties sheet description says Windows USB Driver User Library"Windows USB Driver User Library". The version number would suggest mine came from a package released for Vista (despite the date being too early), while yours looks like something released for W7rtm.

    That file is NOT mentioned in dencorso's thread about usb updates at https://msfn.org/board/topic/162733-usb-functional-patches-for-win-xp-after-sp3/ , nor at https://blogs.msdn.microsoft.com/usbcoreblog/2009/11/13/list-of-the-latest-usb-hotfixes-for-each-windows-version/

    I do NOT have the item in Add/Remove Windows Components, but Add/Remove Programs does have "Microsoft WinUsb 1.0". Unlike the other program entries there is no information about size, frequency of use, last used date, etc.

    • Like 1
  21. @glnz -

    Yes, try what Dencorso suggests to scrub any traces of the new version. It sounds to me like when you reinstalled it got the new version again. Like so many other security apps these days it may immediately "phone home" to check for newer versions and "help" you by fetching the newer version to replace the "old" one. If there are no install options to avoid this you may need to use the trick I use to keep old versions of Avast running. (And yes I do still put Avast *6* on my new builds of XP, and it does not refuse to install the old version for me.)

    Are you using the same old installer from before? If you can't find it, visit https://filehippo.com/download_malwarebytes_anti_exploit/ and try looking at the list of versions on the right side of the page for the one you want to use.

    When you are ready to install, first disconnect your ethernet cable or other internet access. Second, look at the signature date on the installer file. (Right click, Properties, select tab Digital Signatures, move the scroll bar to see the timestamp.) Adjust your system date/time to when that version was freshly released, then install. Go through the settings to disable auto update features, at least for program version updates. For Avast I would now manually insert a previously obtained license key, I don't know if MBAE uses one or not. Reboot if needed. Once all settings are okay, adjust system date/time back to the present, optionally reboot once more, and re-establish your internet connection.

    • Upvote 1
  22. On 11/10/2016 at 3:22 AM, heinoganda said:

    KB3197835 for IIS (Internet Information Services for Webserver-, FTP-, E-Mail-, WebDAV- and Index-Service.)

    Info: This component is installed and executed by POSReady 2009 by default, whereas in Windows XP Professional it is installed later and thus the update is available only with WU/MU if this component is present.)

    I am as usual a bit behind on my updating... but has anyone else noticed that the KB and bulletin referenced by the summary and even by the update catalog itself no longer exist? Even tried both Wayback and Google cache, no luck on either, nor any of the other sites that usually replicate such content - does anybody know what was the issue this update addresses? Or any place to find the missing KB and/or bulletin?

  23. You may just be outta luck, the i810 chipset was a quirky thing in terms of memory. I have an old Dell Dimension L500c based on this chipset, it is specced to take 2x 256MB for total 512MB, but I have never been able to make that work. Two identical sticks, either can run perfectly in either slot (checked with multi-day runs of Memtest86+) but when both sticks are used together all heck breaks loose. Swapping them between slots did not help for me. Not likely the wifi card as I never had one in mine but still have the same problem. I had a similar situation whether running W98SE, or when I temporarily had XP installed, which due to greater memory needs would get into trouble even faster. Mine had plenty of HDD space/swap space so not that either. I didn't use OpenGL so can't speak to that.

    I did note some oddities in the pattern of errors in Memtest86+ with both sticks that made me think there is a defect in the cache, but I don't have any way to change any of that. About the only workable (non)solution I found was to use just a single stick.

  24. My best/favorite machine is running W2K. It is hardware capable to run XP, Vista, W7, 8 or 10 but I like W2K. Yes there are other newer machines in the house running XP or W7 but they are not as good. It has been down twice for power supply issues, once for HDD failure, and a few shorter outages for power failures, but otherwise has been running W2K continuously since its initial build in 2007.

    I have a couple others that also run W2K although they are older and do not see daily use any more.



×
×
  • Create New...