Leaderboard

the government doesn't plan to shutdown networks, but ISP may fear of being disobedient of that order.

Sorry, I thought that almost everyone was aware of OnlyFans now! Yes, it's a site often used by 'adult' performers, but not by any means exclusively so. It was working fine in 360Chrome the last time I looked a few weeks ago, but no longer. Turing all the extensions off makes no difference. It's certainly not blocked by my ISP, if it was I would get a block message from them. Still works fine on my Windows 10 browsers of course.

@Jakob99 The ACPIEx.sys driver when I tried it myself didn't run at boot because it has no HWID to bind itself to. I don't know which HWID it's supposed to be installed for on a real Windows 8.1 system (e.g. ACPI_HAL\PNP0C08). Can you boot your computer into a Windows 8.1 or newer WinPE and share screenshots of the Device Manager's ACPI x64-based PC device? It will also help to share more screenshots about a System Device named 'System board' from the Device Manager. It's for the 'Parent' property and potentially some other device properties. But in any case, I think the only remaining part to be modified for the ACPIEx driver is the ACPIEx.inf file. If it gets correctly rewritten with a real Windows 8.1 HWID for ACPi, then the SpbCx driver will be able to run. And since Intel Serial IO drivers require the SpbCx driver as a dependency, this will make them work too.

I managed to create a modified Intel Serial IO driver that installs without problem, although it required more drivers to be modified first: https://www.udrop.com/KoWZ/Intel_Serial_IO_A368___A369-Win7-testing.rar (md5: e1a87e992db972e867e8710d69c1bc4f) It needs to be tested since I don't have a real Intel Serial IO hardware to try, so one thing you can do is: Shutdown your main Windows 7 OS Boot from a WinPE and backup to USB all the registry hives of your Windows 7 OS in C:\Windows\System32\config This includes all .LOG, .LOG2, .BAK etc files (they're cached transaction logs that are waiting to be written for real). Boot your main Windows 7 OS again This way if you have any problem with the drivers, you can easily do a Registry-only restore with the backups. You can also do a full system partition backup prior to installing the drivers if you wish. The install order that needs to be followed is: Remove all previous versions of the iaLPSS2_I2C driver with DriverStore Explorer: https://github.com/lostindark/DriverStoreExplorer Select ACPIEx.inf and right-click it, then use the "Install" menu item Select SpbCx.inf and right-click it, then use the "Install" menu item Reboot Run dpinst64.exe in the 'Intel Serial IO' folder or it install manually with the Device Manager (devmgmt.msc) Reboot If needed, you can also install the included 'MS HID I2C' driver after Intel Serial IO. Optional: use Driver Signature Enforcement Overrider to self-sign the drivers: https://www.softpedia.com/get/Tweak/Video-Tweak/Driver-Signature-Enforcement-Overrider.shtml Sign only the .cat files if needed. Intel Serial IO A368 & A369-Win7-testing.rar

SpyBot - Search & Destroy Free Edition SpyBot - Search & Destroy Free Edition is an on-demand anti-spyware scanner. It searches your hard disk for all known types of spyware, adware and potentially unwanted programs. It offers powerful features to remove these threats and thus protect your privacy. It automatically detects: adware networks, attempts at host redirection, registry modifications, and unwanted changes in the browser configuration of Internet Explorer and Firefox. If an attempt is made to redirect your computer to a different Domain Name Server without your permission, Spybot can detect and stop this happening. It also protects your privacy by removing these tracks. SpyBot - Search & Destroy 2.4.40.0 is the last compatible version with Windows XP (and Vista) and free of charge. It still receives latest definition updates in these days as reported by @Cixert. Comparison of features: Homepage: https://web.archive.org/web/20140703163113/https://www.safer-networking.org/ https://web.archive.org/web/20140701051907/http://www.safer-networking.org/private/details/#Free Version number: 2.4.40.0 Date of creation: 24.06.2014 Date of release: 01.07.2014 System requirements: Windows XP, Windows Vista, Windows 7 and Windows 8 Release notes: https://www.safer-networking.org/new-spybot-2-4-fixes-several-updating-problems/ Review: https://softchamp.com/download-spybot-search-and-destroy Download links: Installer: http://updates3.safer-networking.org/spybot1/spybot-2.4.exe Offline updater for antispyware definitions: https://www.safer-networking.org/updates/files/spybotsd_includes.exe Instructions for offline updating: Apply the executable spybotsd_includes.exe. Select the programme folder of Spybot – Search & Destroy. The files will be added to the Includes folder within the Spybot program folder. Screenshots: SpyBot - Search & Destroy was written by the German software engineer Patrick Michael Kolla, and is distributed by Kolla's Irish company Safer-Networking Limited. I used SpyBot - Search & Destroy a long time under Windows ME and some years under Windows XP. It served me well in those days. Thanks to @Cixert for reporting that SpyBot - Search & Destroy 2.4.40.0 is the last version which still receives definition updates in 2023! Cheers, AstroSkipper

It's potentially normal behavior that the modified Skylake Intel Serial IO driver of Windows 7 didn't work because of the modded DSDT. I'm just making a guess about the DSDT & this Intel Serial IO error code 31, but it might very well really be because of this. On Windows 8.1 the driver might already behave correctly with a DSDT that returns the "Windows 2013" profile. In this case it's a matter of manually adding the missing HWIDs as you did, and it should work. But if the driver runs on Windows 7 and the DSDT returns a "Windows 2013" profile, the driver will still try to run as if it was "Windows 2009". It's best to use a Windows 8.1 Intel Serial IO driver, and it needs to initially be intended for Windows 8.1. If the Intel Serial IO driver doesn't care about Windows 7, then it will directly use the proper code for your DSDT's "Windows 2013" profile. Then it's just a matter of modifying the Windows 8.1 Serial IO driver to work on Windows 7 anyway. I found a Windows 10 driver that already supports PCI\VEN_8086&DEV_A368 & PCI\VEN_8086&DEV_A369 natively (very early version from 2017). There's also a Windows 8.1 driver that doesn't directly support these HWIDs but it comes with PDB files (debug symbols). I'm going to sort these out to select the best one for Windows 7 backporting, it shouldn't take very long. Another note is that MediaFire blocked your download link because of DMCA. MediaFire really seems to dislike the upload of Intel driver files (it's not the first time this happens). MEGA.nz also sometimes blocks Intel driver downloads. Next time you will need to password-protect driver uploads with any archiver of choice that supports .7z or .rar format. Use the 'encrypt filenames' option & put any password such as 'driver'. You can also name the file 'Outtel Serial IO 7th Gen+ Win 7' if needed, or any other 'Intel' wordplay of choice.

Nothing in my reply was angry or uncalm.

I looked it up deeper and the driver fails to load likely because of the lack of a KB3125574 Windows update: - https://www.catalog.update.microsoft.com/Search.aspx?q=KB3125574 This update brings a WdfLdr.sys driver that the Intel HID Event Filter relies on. However it should work without the KB3125574 update by taking it from a Windows 8.1 system. I took your Intel HID Event Filter drivers and modified them, the list is as follows: Removed all invalid INF comment prefixes // and replaced them with ; instead Added my compiled ntoskrn8.sys & WdfLdr.sys from Windows 8.1 to the INF files section For HidEventFilter.sys & WdfLdr.sys I modified the EXE/SYS file headers to use MajorVersion 6 & MinorVersion 1 Because it was MajorVersion 10 & MinorVersion 0 (6.1 vs. 10.0 for Win10) Modified the import filename in both HidEventFilter.sys & WdfLdr.sys from ntoskrnl.exe to ntoskrn8.sys Modified the __security_cookie in both SYS files & bypassed the security cookie check in driver code as well Removed the Security Directory information from EXE/SYS headers for both HidEventFilter.sys & WdfLdr.sys Updated all the EXE/SYS file checksums in the headers for all files Created a new unsigned HidEventFilter.cat file with '6.1' OS attribute (verifies all .sys files & the .inf file) Included dpinst64.exe from Microsoft (version 2009 for Windows 7 64-bit) Prior to installing the modified drivers, you need to remove all the previous Intel HID Event Filter drivers with DriverStore Explorer: - https://github.com/lostindark/DriverStoreExplorer This allows for removing old drivers that otherwise get reinstalled again instead of the newest modified drivers. The modified Intel HID Event Filter drivers (version 3): - https://www.udrop.com/KopH/HidEventFilter-Win7-testing-3.zip (md5: 765c950f421cd7a9b7a353e8e980487c) For the 0x0000007E BSOD error code, it doesn't actually mean much other than 'Windows had a trouble while running this program/driver'. It's a generic Windows error code rather than one that actually gets sent by the Intel HID Event Filter itself. Try the modified version after having removed all previous ones with DriverStore Explorer, I think it should work. You can also enable testsigning & easily self-sign the drivers yourself with Driver Signature Enforcement Overrider: - https://www.softpedia.com/get/Tweak/Video-Tweak/Driver-Signature-Enforcement-Overrider.shtml Just sign the HidEventFilter.cat file only if needed. HidEventFilter-Win7-testing-3.zip

That's because it's only 18+. BTW, you confirmed what I thought, it's indeed CF doesn't like something from Dave's network.

I always thought @Dave-H is a musician. Looks more like the infamous "just a moment" cloudfare protection fingerprinting. https://community.cloudflare.com/t/checking-your-browser-before-accessing-on-loop/281082/13 https://www.reddit.com/r/CloudFlare/comments/103vsgx/need_help_with_browser_check_loop/

Radio chatter: "We've got a runner here that tried to access onlyfans.com. Proceed to investigate." From Wikipedia:

Works for me. Maybe try with a fresh profile or just run the browser temporarily with --disable-extensions command-line parameter.

well, I think managed to make it work correctly, it was some kind of incompatibility with "4t tray minimizer". I reinstalled both and now its working.

It seems the error logged is a red herring. The exception is just reporting that the program crashed. not what lead to the crash. Debugging game issues can sometimes be an issue. The first thing I do is look to see if any log files are being generated. These can be in the steam folder, in Documents, or in either Local or Roaming Temp folders in AppData of the user account. If you are lucky, you may be able to find a clue this way, or if really lucky you can find a dump. Unforuntately, debugging anticheat aspects can be especially difficult since if you were to attach windbg to it, this is enough for the anticheat software to stop the game from launching.

My definitions are now 4 days old. Manual update is not working. Also, I created a Microsoft account this weekend. Successful, but when I tried to enter my landline number, it tried to text me a security code. I do have a cell phone now, but it is for emergency use only. If I start handing out that number, I might start to get calls on it, which I do not want.

Should read "WDDM is..." (WDM is an unrelated driver model, not a display model at all.)

I checked that file, and it remains unchanged, even when I install all of that 6003 series upgrades. (looks like it's from the original SP2, released on April 2009)

I tend to disagree, I noticed the overall speed of booting increased, some games gave more FPS, not like it's night a day difference, but noticeable on my old PC, especially good when used with ex-kernel. It's trial and error, actually, I had to test lots of them, before I found that good one.

Found an easy and fast way to replicate SP2 with nothing, except: Install in order 1 - KB971512 2 - KB2117917 3 - Apply redirecting via registry 4 - Install one of these non-beta monthly rollups (like KB4487023, KB4480968, kb 4493471). 5 - Reboot 6 - Place kernel, shell, user locally, you will see no dialogs open at all.

Good to know. Upon further investigation, I notice the Event Log there's an Schannel Fatal Alert 40. It only happens when I press the update button in Windows Defender. At the same time in the Windows Defender "Operational" Logs, there's an error under Event ID 2001 at the same time. I still can update manually though. I wonder what changed.

Why 1809? Chromium 117 works even on TH2 version (1511). So maybe this API is not needed after all

Has anyone not been able to update Windows Defender on Windows 8 for the past week or two?

Could you please describe in details? What did you mean "kill Vista"?

And what are business consulting firms for? No one would risk such vast amounts of money without doing a proper research first.

Your driver is missing this dependency *shown in red on you photo. https://www.google.co.uk/search?q=dependency+in+programming

In any case, save this driver, you might need it in the future, it's a very rare one for Kaby!

just add your device ID, if it doesn't find it! there's 1000000 millions of tutorials about it.

You're welocome! Official sources is what always preferred on this forum! Enjoy.

I was thinking that you could make a short video of when you do these updates, and create a Youtube channel to publish these videos, the simple text description may not transmit to the audience enough the emotions you feel when implementing these updates. Besides (right now) the site gives a 404: jaclaz

Still : https://dictionary.cambridge.org/dictionary/english/enthusiast and punctuation/capitalization would IMHO need a check or two. jaclaz

Good start, keep 'em coming. But please watch the typos, it is really a pity when the reader fails to appreciate the contents because he/she is distracted by them, I counted at least 5 issues in: jaclaz

I see, it is a long term plan, halfway by Easter and the other halfway hopefully by Christmas 2023 Do post here every time you add something, it is important to document each step, so that we might later be able to make a documentary on "the making of". jaclaz

Viewing WHAT? The Few Things being ANY meaningful content. But please do keep up posted on the progress. jaclaz

Great! Congrats! You did it!

Did you install a security program like Eset, Malwarebytes or Avast? These programs have a lot of features, one of them is a HTTPS Scanning feature and can be problematic if connected via HTTPS.

The meaning of your error code: 0x80072F78 = ERROR_HTTP_INVALID_SERVER_RESPONSE = The server response could not be parsed. Anyway, you have connection problems to MU server. Check your firewall settings and disable security feature called "https scanning " in your security software if existing. Try to disable Windows Firewall temporarily while accessing MU web site. And please upload WindowsUpdate.log!

Alright, I see, proxy is deactivated. I thought it is activated.

Ok, actually it should look like mine:

Thanks, but I will not provide download-links to Russian servers anymore. Sorry, it's very sad but we must make a mark, no matter how small it is! Besides, the changes are minor and can be done by users themselves according to their needs. Generally I try to provide download-links pointing to locations of original sources. But anyway, thanks for your offer! BTW, a modified and updated version of ProxHTTPSProxyMII 1.3a (20150527) for old computers which haven't got a CPU with SSE2 instruction set, will be soon released by me when test phase has been successfully completed.

No new Easter egg from me! Either I've been just a bit too careless while writing and correcting or it is due to a kind of senility! Thanks for reporting again! I'll correct that immediately, of course! No, the fixed version of cacert Updater can be downloaded from first post in my thread in section Downloads: The changes are minor indeed and can be done simply by applying cacert Updater Fixed. BTW the AIO package has been created by @Windows7fan from MDL. Therefore maintaining of it isn't my job. And I totally agree, if actions are performed manually, users get full control because one knows what has been done and what has to be performed next. Very important if verifying of each step is necessary.

I am so sorry! Truth to be told I really thought you are female because of your name Mina (read in forum "Introduce Yourself!") meaning "heaven". Once again, I have to apologize to you! Do not be angry! Appearently I am not a Sherlock Holmes. Wow! You are the only one who has found my easter egg! That means you have really read my guide carefully! Thanks for reporting! Good luck! Hope it will work this time! Kind regards, AstroSkipper

In fact, an early build of chrome51 works fine on vista chrome51 2679