Leaderboard

Roses are red, your glasses are blue ... I don't sleep at night 'cause I'm thinking of you'.

Hello, i've been recently messing with a Z690 motherboard and an Intel Alder Lake CPU Managed to get Windows 7 installed, but it was tricky, decided to try an updated Windows 7 ISO with drivers (USB3, NVMe... etc) slipstreamed and tried out, found out Intel USB3 got updated enough that current driver infs lacked the IDs for the new chipsets and didn't recorgnize it, so i had to install using from another PC with modern Intel AHCI, then carry the drive over the system after the first stage of setup. I ended forcing one of the AMD USB3 drivers with success on the system. Test machine specifications: Intel Core i7 12700K 32 GB DDR4 3200 MSI Z690-A PRO DDR4 (Budget Z690 with decent VRM, DDR4 and PS2 port) GTX 1060 3 GB 120 GB SSD (Kingston SSDNow V300) What i could get working: SATA/AHCI HDA Audio Most chipset stuff USB3 (After forcing AMD XHCI Driver), although there are issues What didn't work: Onboard LAN (unsupported Intel controller) IGP (that is expected though) Few unknown devices Untested: NVMe Known issues: USB stops working after resuming from suspend (at least with AMDXHCI driver) Single thread workloads may not allocatte in the right cores USB3 setup, first attempt: Setup after doing 1st stage setup and moving the SSD to the ADL system: After finishing setup: End results: WEI score:

replace the msvcrt.dll by the v3.0f msvcrt.dll

I see D.Draker uploaded it for you. (Thanks!) It won't make any difference, though, unless you need it to validate another certificate that was signed by that one. I understand. I don't think there's any problem with ProxHTTPSProxy. I think there's a bug with Windows Update when it tries to validate a site certificate signed by your ProxHTTPSProxy certificate that runs from 2021 (last year) to 2031. It's throwing that date/time error code when it shouldn't be; your ProxHTTPSProxy certificate is fine but WU still chokes on it. As to actually finding that bug and fixing it, where's @mixit when you need him? For some reason, WU seems to like the original ProxHTTPSProxy certificate (the one that runs from 2015-2025) better. But, it won't work unless you put it in your trusted root store (with a command like the one D.Draker gave you for the M$ certificate) and also recreate your site certificates. I think ProxHTTPSProxy will re-create your site certificates automatically if it sees that CA.crt has changed, but just in case, you can rename your ...\Certs folder and create a new, empty one. That will force ProxHTTPSProxy to generate all new site certificates and sign them with the new CA.crt. The reason for renaming the folder vs. just clearing it is just for performance; if things go wrong, you could just delete everything in ...\Certs, but if instead you go back to your current configuration, ProxHTTPSProxy won't need to re-create all your site certificates yet again. If you have to put your current CA.crt back, it can just go back to using the old ones. A final note: CA.crt contains both a certificate and its private key. The private key is needed to sign the site certificates that ProxHTTPSProxy creates. From a pure security standpoint, it's unwise to share a file with a private key like CA.crt, because (in theory) any two folks using the same CA.crt could decrypt each other's communications, if they had access to each other's computers. But for what we're doing, it's probably fine. I doubt that any of us is inclined to spy on anyone else! That said, does anyone using ProxHTTPSProxy have a CA.crt expiring between 2025 and 2031? It'd be interesting to see if it works or not. I suspect there's a particular point in between (1/1/2028?) where things go wrong.

@maile3241 Fine but is your folder male? :)

found him! He was hidden.

Don't recall offhand. When Windows 7 landed me in the hospital for migraines that i've never had in my entire life until Windows 7's font rendering came along, I promptly returned to XP. I actually thought I had brain cancer when hit with migraines two or three times a day for several days and never knowing what a migraine was! My issues with sub-pixel anti-aliased fonts actually landed me (and others like me) in medical journals - I've kind of always regretted not getting a "copy" just for nostalgia or whatnot. Most people's eyesight just "adjusts" to sub-pixel anti-aliased fonts. It is NOT because my eyesight is "worse" than others, it's because it is more accute and accurate than others. I mean, I can't fly around like a hawk and swoop down for a field mouse, but I guess you could say it's something like that, lol.

@ExtremeGrief I could do that but I didn't. If you want to merge it's up to you. I did it my way as Frankie Boy would say (or better sing). Don't say other people what they should, could or have to do. If you want to do it "better" do it by your own!

It wasn't the nicest comment to make to a fellow forum member, he can consider himself warned, unofficially at the moment. Whatever you may think of others personally, keep it to yourself please everyone, and stay on-topic. If you feel a real need to dispute with someone, take it to a PM, we don't tolerate public slanging matches on threads here.

As far as I'm concerned, "dude" is a slang term, the American equivalent to the British term "mate". Usually fine in informal banter, but not always appropriate in every context, and open to the user being accused of overfamiliarity, and being patronising, during a dispute. This is getting personal, and off-topic of course. I will be wielding my axe if it goes on any longer.

I'm fairly certain that it has also been confirmed as "undignitary" and generally not appropriate in formal speech. Paraphrasing because I have "zero" interest in digging the thread back from the grave just to see how it was "worded". But at the same time, I don't buy into the whole "P.C." aspect of cultural lexicon, so I'm not suggesting that we all need to speak "formally" herein. It personally wouldn't bother me one iota if "dude" was added to the list of words that gets automatically "asterisked" on the forum, but I see both sides. Did find this interesting -- https://everyday-courtesy.com/is-it-rude-to-call-someone-dude/

Well , actually it isn't mine , this link is from this MSFN post , so I think maybe needs to be redacted. MS had the link deleted . I think it's safe to use the mirror someone gave to you . I didn't check myself ,though. https://msfn.org/board/topic/175170-root-certificates-and-revoked-certificates-for-windows-xp/

Status Update - I plan to have updated downloads by later today that basically gets us to a working version with only one exception - today's "working version" will basically be limited to browser profiles that do NOT use NoScript. I still have some digging to do on the combination of NoScript + Proxomitron.

We hear you, D.Draker. I have attempted to point out on a few different occasions that we have different goals for this thread. Proxomitron CAN connect to a REMOTE proxy, but my goal is its usage as a "web filter" 'local proxy'. You do "seem to", intentionally or not, want to "hijack" the thread and steer it towards your goal. Proxomitron CAN be used "towards" your goal, but it was not my intended target audience. I agree with RainyShadow, XP users are already familiar with this topic but were intimidated and confused by Proxomitron when they tried it the first time and so they walked away from Proxomitron. My goal herein is to alleviate that intimidation and confusion and perhaps generate enough interest here at MSFN for Proxomitron to tame the "modern web". Proxomitron is a Swiss Army Knife. It CAN be used to elliminate the need for NoScript, uMatrix, Stylus, Tampermonkey, Adblockers, Popup Blockers, Cookie blockers, Privacy Badger, I could list a thousand (literally!) "extensions" that Proxomitron can elliminate. My target is not to elliminate thousands of extensions - we all use them and are familiar with them. But some of us "power users" would PREFER to not have to have "too many" extensions - they slow down the web browser and consume excessive RAM. I apologize if I mislead you and gave any impression that your Instagram issue falls within my target audience.

I just think your face is kind and you're a charismatic person . ))))) Also , I feel you have a strong will. You are calm , you smile , but your will is strong .

It is "anime" as much as "The Simpsons" is. As Wikipedia says "Inside Job is an American adult animated science fiction comedy streaming television series". It's from your ally Langley That said, i could also recommend you one anime series about bodybuilding, if you change your mind later btw. i just watched "Poisson d'avril" yesterday. De Funes is such a villain, lol. Reminded me of his "Le Gendarme..." movies. Well, remote proxies is the first thing that comes to your mind. I don't mean to offend you, but from the very beginning you mistook this for the thing suited to your needs (which it is not). Most of the regulars of the XP forums either use or at least have heard about ProxHTTPSProxy, and by extension likewise about Proxomitron as it's required for ProxHTTPSProxy. Instagram has a specific policy against that. Even if you think your case is "quite similar to ordinary browsing", the server can clearly detect it and block you. Your whole approach to this problem (Instagram blocking) seems wrong to me. You insist on using proxy lists and automated scraping, and just quickly burn any working proxies you find. This is an annoyance not only to you, but also to everyone else who may have wanted to use these same proxies for normal Instagram browsing. Why don't you open a discussion for this problem exactly (the blocking, not proxies) so you can get specific help on it? And if you don't really care about Instagram, but only about buying sports food, make it about this instead. I am sure you could get much better help this way. HTH

https://greasyfork.org/en/scripts/438991-download-extension-from-chrome-web-store "Script meant for Ungoogled Chromium, but may be used with any browser to directly download Chrome Extensions from Chrome Web Store. It adds a floating button in the bottom right corner which let's you download an extension directly."

Clean Flash Installer version 34.0.0.211 is now available at https://gitlab.com/cleanflash/installer/-/releases/. Confirmed working on Windows XP. Don't forget you need JustOff's GitHub-wc-polyfill add-on installed to access GitLab from a UXP browser; also Serpent 52 must be in single-process mode. 360EE should work without issue.

Are you chatting me up?!

I understand you don't like me ... not sure about the other members ... But why in God's name did you block @Dave-H's face ?!?!? Dave-H looks like a noble British gentleman . Don't you agree ?!?!?!

This thread is a little bit confusing especially for people looking for help. So I have made a complete guide with all tips and steps which have to be performed to restore access to Microsoft Update web site and are working for me. Of course at your own risk without any guarantee! And just to clarify: I am not the author or contributor of these patches and tools. I am a user and have examined my problems while restoring MU in Windows XP. This guide is the result of my examinations to help other users. Of course I did some modifications due to the fact that some patches don't work properly or something is missing. If you want improvements of these tools and patches, please contact the authors! Complete guide for restoring Microsoft Update in IE To be successful in restoring of access to MU web site, you have to keep the order of following steps. Please, do not change this order! 1. Check BIOS and Windows date and time incl. correct time zone. Perform a time sync! 2. If you have used "WSUS server" in combination with "WUMT" in the past remove it completely by "Remove_wsus.cmd". This batch file does not work properly, so you have to remove this registry key manually: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. You can let "Remove_wsus.cmd" perform this by adding following line (without quotes): "reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f". Start Automatic Update service. In system panel Automatic Update may not be shown greyed out. 3. Go to Windows Services. Three system services are absolutely important for MU: bits, wuauserv and cryptsvc. These services should have been started and set to automatic. 4. Configure Internet Explorer. Internet Zone to standard, Trusted Zone to high with only these three urls related to MU: http://www.update.microsoft.com, https://www.update.microsoft.com and http://update.microsoft.com. Credits to @maile3241 and @AstroSkipper. Go to Internet Explorer Options, Advanced. Check if TLS 1.2 is enabled. Uncheck entry "Check for server certificate revocation". 5. Before installing updates apply "PosReady.reg" if not already done. 6. Install these four updates KB4467770, KB4019276, KB4493435, KB942288-V3. Credits to @maile3241. 7. Apply "Tls 1.2.reg". Credits to @maile3241 8. Execute "rootsupd.exe". 9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256. Download link: http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe 10. Install "ProxHTTPSProxy". Download link: https://i430vx.net/files/XP/ProxHTTPSProxyMII_REV3d_PY344.7z, credits to @heinoganda. Here you have to edit the config file "config.ini". Under section [SSL No-Verify] I added fe2.update.microsoft.com and deleted update.microsoft.com under sections [SSL Pass-Thru] and [BYPASS URL]. This is working for me. 11. Download and install one of these packages: an English all in one version, credits to @Windows7fan from MDL, @xpandvistafan, @maile3241 and @AstroSkipper from MSFN: https://drive.google.com/u/0/uc?id=1z5NGORov8OS7iBkoFVsvWOTOE1_LCjoQ&export=download or a German all in one version, based on version above, modified and updated by @AstroSkipper: https://www.mediafire.com/file/0y1zmwv8z4lch9s/Restore_WU_XP_DE.7z/file. Credits to @Windows7fan from MDL, of course. Here you have to check if "install.cmd" did its job properly i.e. all commands in "install.cmd" should have been performed completely. Additionally you have to verify the existence of patched "wuaueng.dll" in both folders system32 and system32\dllcache in form of a binary comparison.. Be aware of SFC which tries to restore an original old version of this file! After patching restart your computer and recheck! Verify if really all registry entries have been added.i All bold files mentioned here are in these all in one versions included. They can be installed manually (all registry entries of "install.cmd" have to be added manually too) or automatically by applying "install.cmd". 12. If you have problems in configuring ProxHTTPSProxy, or you get error code 0x80072f8f while trying to access MU web site, have a look in my thread: 13. Use "CAupdater" or "Certificate Updater 1.6" to update your root certificates. Download link of Certificate Updater 1.6 can be found here: 14. If the button "Check for updates" doesn't work on MU, close Internet Explorer, open MU from Start Menu again and in most cases it will load successfully. 15. If you have a fresh installation or a reinstallation of Windows XP, it seems to be necessary to install MU ActiveX Control manually because it won't be downloaded automatically any longer. Without any confirmation by me (no opportunity to check it), here is a guide how you can do that. Credits to @maile3241: 16. If on MU web page error code 0x80072F78 appears, turn off your firewall temporarily. If MU is working now, add the program "wuauClt.exe" into the exception list of your firewall and turn your firewall back on. In any case ProxHTTPSProxy or HTTPSProxy must not be blocked by your firewall. Same for Internet Explorer, of course. If on MU web page other error codes appear, rename the windows folder "SoftwareDistribution" to "SoftwareDistribution.old" and let MU generate a fresh one. Maybe you have to disable a "HTTPS scanning" feature of your security software temporarily or make exclusions for MU related sites. 17. Do not use the same "DataStore.edb" in "SoftwareDistribution" for WSUS server/WUMT and MU web version. I have two DataStore.edb files, one for WSUS server and one for MU. One for all doesn't work in my system. 18. Use only http-links to open MU in IE. Direct link is http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en or http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1 19. MU is only working if ProxHTTPSProxy is enabled. 20. For testing I add a link of my working ProxHTTPSProxy's config.ini: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file 21. If completing all of these steps didn't help you at all, even after repeated execution, you may have a rather general problem relating to MU in your Windows XP installation. In this case you can try to manually reset Windows Update components. Here is my post how you can do that: After that kind of reset I recommend to perform all steps once again (from step 1 to 20 inclusive). Of course, some steps won't be necessary any more but checking which to perform or not will cost a lot of time, therefore senseless. Although I am not a friend of automatisms, I also offer a tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to backup your system partition completely at first. This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk. The last XP compatible version is 10.5.3.7: https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file and a less recent version 10.5.3.4 with a help file included: https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file 22. If unfortunately none of all these 21 steps helped you, then you should presumably think about a complete reinstallation of Windows XP. I did all these steps (except steps 21 and 22) and for me MU is working flawlessly in my Windows XP Professional system. For further detailed instructions and missing files perform a search in this thread and enjoy the screenshots we all have uploaded! If you enjoyed this guide or maybe you found it interesting and helpful, I would be pleased about any reaction by liking or upvoting. Greetings from Germany, AstroSkipper PS: This guide will no longer be maintained. It will stay here just for historical purpose. The new, maintained and up-to-date version can be found here:

Probably, never looked into it. The author of the program presumably put it there because bad actors apparently love trying to use his program as the vessel for bad stuff. Yup, it's not saved anywhere. I may take a look next weekend.

I have a problem with my old computer, it does not have a working CD reader, and it has Windows 95 , and at the same time it's Pentium 2 , it cannot and does not have a USB boot feature in the BIOS.. I could not install Windows NT 4 yet. I have a big problem with time, I started working in a web development company and studying at the same time. I'll try to install Windows NT 4 later, and I'll tell you if it works or not. If Windows NT 4 succeeds in creating the memory.dmp file, I will get the new baseAddress, and the new kernel32 will work. I hope it works

Ouch, I’m assuming it’s the same for NT 3.51? I really wan’t to do a mini kernelex for the OS, but I wan’t to know if windows2 can get the modified NT4 kernel32.dll to work first if that is the case. I hope so too.

I will try with an old computer, I hope it will work well, and I hope the operation will be successful. Otherwise, there would be no other way to find out the new BaseAddress !

If this is what I think it is (NT 4), then I think it may not be possible to generate a dump early in boot. I could not in Vista when it was time to initialize ntdll as well. If you bugcheck early enough, no text will be printed on screen except for the four bug check parameters.

@win32 Hi, have you an idea about how to make VirtualBox to creat the MEMORY.DMP file , I went to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled and changed the value to 1 ,but it didn't solve the problem , I need to know the new BaseAddress of the kernel32.dll with WinDbg to solve the problem .