Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

heinoganda

Member
  • Content count

    558
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by heinoganda

  1. @Destro The two updates, KB4056615 and KB4074852, I have in a Windows XP installation medium integrate. The result was one of my slowest installations of Windows XP. In the beginning, there was no difference, but the first regular start was the system stuck, after a user could finally be created ran Windows as in slow motion because many services started very slowly. Various reported software like MBAM 3 did not work.
  2. In my VM, after reinstalling Windows XP sp3 and installing updates, the bugs also occurred. I work with my own update rollups that are installed after the installation of Windows XP sp3. Maybe I can help you with this info, myself I do not do any time-consuming work with Slipstreaming of individual updates anymore.
  3. My God, do not be so petty. So you could try your latest security enhancements on your machines an hour earlier, until they answered with a blue screen. Then the holiday was relaxing again for naught. Note: I tell Microsoft that the clock has to be turned back 3 weeks for you.
  4. Cumulative timezone update KB4074837 released. (For Namibia, Turks and Caicos) http://download.windowsupdate.com/d/msdownload/update/software/uprl/2018/01/windowsxp-kb4074837-x86-embedded-enu_7d231ab54a6f0b4d967d3165ee89f8e08dedaa65.exe Note: MS should rather offer functional replacement for the broken updates.
  5. I downloaded the Safe Uninstall Utility and backed it up to web.archive.org. Since the link went to an e-mail (disposable address), I'm not sure if I should publish the download link. Maybe you still remember a few versions of Rapport that would be of interest. Otherwise the Rapport Safe Uninstall Utility works, then I do not need to uninstall it manually. Then I'll test something in my VM, if I can trigger your problem.
  6. In my VM I noticed with the versions 3.5.1804.xxx that they could not be uninstalled. There were no problems with the 3.5.1609.xxx versions.
  7. Open the file "RapportSetup-Full.cmp" with 7zip 9.20, unpack "RapportSetup-Full" and rename it in "RapportSetup-Full.msi" As far as a version number is known, the download should be possible accordingly.
  8. I took the trouble to find a download link where you can choose the version (RapportSetup-Full.msi). Since only the downloaders are available via web.archive.org, follow the link to the Full Installer: After the download, open the file "RapportSetup-Full.cmp" with 7zip 9.20, unpack "RapportSetup-Full" and rename it in "RapportSetup-Full.msi".
  9. For your information, this error occurs under Internet Explorer 8, traceable after a reinstallation of Windows XP. Installed is the Windows Update Agent v7.6 (Info). Furthermore, I create my own update rollups (which it certainly is not), as a little note. Maybe even a user has to deal with this problem, then at least there is a solution. @mixit Have also made a test with the Comodo Firewall 8.2.0.4591, with the original update KB4074852 it comes to your described error message, with the manipulated KB4074852 it works.
  10. Info on the edge, who carries out WU or MU over the Internet Explorer is currently tormented with the Error number: 0x80072F19. To circumvent this problem WU or MU should be called via https! https://update.microsoft.com/windowsupdate https://update.microsoft.com/microsoftupdate
  11. For experimental users I have modified KB4056615 and KB4074852. For KB4056615, the original NTFS.sys (The version was changed from 5.1.2600.5512 to 5.1.2600.7392) file was implemented, as well for KB4074852 the file oleaut32.dll (The version was changed from 5.1.2600.7248 to 5.1.2600.7424) and KB4018556-v2.CAT (name adapted to KB4018556-v2x.CAT) copied from KB4018556-v2. Available for the Windows language version ENU, DEU, ESN, FRA, ITA, NLD, PTB, PTG, CSY, DAN, ELL, FIN, HUN, NOR, PLK, RUS and SVE. AU, WU and MU are no longer offered after the installation of the modified updates KB4056615 and KB4074852. Before installation, the two original must be uninstalled before! If interested, send me a PM.
  12. @XPosed I hope you have installed Microsoft Installer 4.5 (KB942288-v3). At the moment it is best to dispense with KB4011715 and KB4074852 until repaired updates are provided by MS. Then, just a lot of fun remains the taste. @Dave-H Have tried for a while, but I can not retrace your problem. I think you have already tried KB4011715 and KB4074852 to uninstall. Maybe you have already tried to reinstall Desktop Search 4 (KB940157 + KB963093)? Maybe a past update was not installed correctly, can happen with various virus scanners. Otherwise, I can not offer a solution at the moment.
  13. @dencorso The problem with KB4074852 I can confirm once again on my host computer and in my virtual machine (VMware Workstation)! If you want to install KB4074852 The file "oleaut32.dll" version 5.1.2600.7424 makes the problems described by you! I kept the original file "oleaut32.dll" version 5.1.2600.7248 of KB4018556-v2. Malwarebytes 3 works just as smoothly. As always no guarantee, at your own risk! Personally, I remain, as KB4056615, very critical at such solutions!
  14. Unfortunately, it does not change the fact that KB4056615 is faulty. Additionally, it is likely that the vulnerability will no longer be resolved with this partial security update.
  15. @wyxchari It's none of my business, but why are you doing a support request at Malwarebytes, knowing that KB4074852 is buggy? Especially since the updates for POSReady 2009 are not official for Windows XP. I would not be surprised if Malwarebytes, as it was the case with Palemoon, can not install anymore if the POSReady key is present. If so, then contact Microsoft Support if you have a device where POSReady 2009 is installed according to the terms of the license.
  16. @Dibya @glnz @niko32 Because of the problems with KB4056615, various information has been published in this topic. 1. Problems with the NTFS file system 2. For some OEM systems, the installation had to be enforced (option -o was needed, for me an indication that this update does not seem to have gone through all the checks in MS) 3. Has nothing to do with Meltdown and Specter. Info / CVE-2018-0748 Read from here: As far as the problems with KB4074852 are concerned:
  17. Now there are two updates that require a revision. KB4056615 Severity of the vulnerability is high KB4074852 Severity of the vulnerability is very high Since January 2018 there is no month, where not at least 1 update makes problems. Mistakes happen, but here MS should provide working updates at short notice!
  18. This can happen if changes are made to an Office package or if you install an Office package.
  19. Since I have the whole thread no correct solution for the update of the Roots certificates and revoked certificates found, I hereby would like to offer a way to keep them up to date. For the security of Windows XP after the last condition no official patches more for blocking div. Roots certificates and certificate update available. For revoked Certificate Update "rvkroots.exe" Microsoft download (http://www.microsoft.com/download/details.aspx?id=41542), unzip to a folder (eg with WinRAR), in "rvkroots.inf" entry in the string VERSION should "5,0,2195,0" loud and in VER "005". The next step is download the "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcert.sst" and paste the unzipped folder and replace older file. Then with e.g. (Create Self-Extracting Archive) WinRAR all files in the folder to an archive option SFX with the following comment: TempMode Silent=1 Overwrite=1 Setup=Rundll32.exe advpack.dll,LaunchINFSection rvkroots.inf,DefaultInstall pack and you have a current update for blocking unsafe Certificates! For Root Certificate Update "rootsupd.exe" Microsoft download (http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/rootsupd.exe), unzip to a folder (eg with WinRAR), in "rootsupd.inf" entry in the string VERSION should "40,0,2195,0" loud and in VER "040" , In the next step, "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authroots.sst" "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/delroots.sst" "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/roots.sst" "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/updroots.sst" download and paste the unzipped folder and replace older files. Then with e.g. (Create Self-Extracting Archive) WinRAR all files in the folder to an archive option SFX with the following comment: TempMode Silent=1 Overwrite=1 Setup=Rundll32.exe advpack.dll,LaunchINFSection rootsupd.inf,DefaultInstall pack and you have a current root certificate update! For all languages! If you do approximately every 3 months. To re-update extends the generated SFX files to open with WinRAR and drag to the archives newer downloads (.sst files) by drag and drop into it.
  20. Root Certificates and Revoked Certificates for Windows XP

    Update for root certificates: Delete: OU = RSA Security 2048 V3 O = RSA Security Inc CN = Swedish Government Root Authority v1 O = Swedish Social Insurance Agency C = SE CN = WellsSecure Public Root Certificate Authority OU = Wells Fargo Bank NA O = Wells Fargo WellsSecure C = US CN = WellsSecure Public Root Certification Authority 01 G2 OU = Wells Fargo Bank NA O = Wells Fargo WellsSecure C = US New: OU = certSIGN ROOT CA G2 O = CERTSIGN SA C = RO Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.
  21. Microsoft patches Windows XP to fight 'WannaCry' attacks

    Well, I'm worried because so many old barrels can also have an unpleasant content. The following example shows fish specialty from Sweden.
  22. Microsoft patches Windows XP to fight 'WannaCry' attacks

    Actually, I do not understand why an old barrel is reopened. For this problem, there were even official updates for Windows XP sp3 (users who received the updates for POSReady 2009, got updates a little earlier)! Currently KB4012598 has been replaced by KB4041995 from 10/05/2017!
  23. Microsoft security essentials and Windows XP

    As there was a demand for a German version of MSE in this topic, it is just a different language version.
  24. Microsoft security essentials and Windows XP

    Have times with my local proxy the download link for MSE v4.4.0304.0 German extracted from Microsoft Update, here it will be offered to me after the search under software optional. Download from MS: http://download.windowsupdate.com/d/msdownload/update/software/ftpk/2013/11/mseinstall_17f531645ed7e5b4043adecd21bcea2fc21b50f1.exe Download over web.archive.org: https://web.archive.org/web/20180130200636/http://download.windowsupdate.com/d/msdownload/update/software/ftpk/2013/11/mseinstall_17f531645ed7e5b4043adecd21bcea2fc21b50f1.exe @mo832 Have you tried using the MSE Updater to reset the Antivirus Update Engine (RAUE)? Then update the Virus-Definition for MSE (1).
  25. IE 8 in 2018?

    @apreese16 Disable automatic updates and reboot. Now MSI 4.5 (KB942288-v3) should be installed, then manuel the latest update of IE8 (KB4052978). Make sure that TLS 1.0 is active in Internet Explorer 8. Now the search should work with Windows Update in Internet Explorer 8. If you have the Microsoft Office Compatibility Pack or Office 2007-2010 installed, Microsoft Update may resolve this problem again. In this scenario, you must manually install the latest updates for these products from October 2016 or go back to Windows Update. Note: You can not just enter the POSReady entry in the registry, a detailed manual has been to the "POSReady 2009 updates ported to Windows XP SP3 ENU" published!
×