Leaderboard

I have been playing around with a dual-boot msdos 6.3 + 7.1 boot system. to help with a help file. There are things to do with these DOS versions yet, but the help-system from 6.22 has been updated to include most of msdos 5.x to 7.x, as well as interesting info on pcdos, versions of programs like emm386 and msd, which shipped with dos, and even basica / gwbasic, etc. http://www.os2fan2.com/files/dos7help.zip is the source. The version of qbasic has a number of known patches applied, inc;luding the *.* and phatcode patches. dos6.com is help.com, renamed so not to overwrite help, and so it's accessable from 4dos as well. qbed.com is edit.com renamed to not overwrite edit.com. The help and ini file are qbed.hlp and qbed.ini, for similar reasons. W

NTOSKRNL Emu_Extender Library of missing functions for Windows XP/2003/Vista/7 NTOSKRNL.EXE Project is intended to help in porting drivers from Windows 7/8/8.1/10 for work with Windows XP/2003/Vista/7 How-To: Compile sources to make ntoskrn8.sys Make corrections to target driver XXX.sys so that it loads ntoskrn8.sys instead of the original ntoskrnl.exe If XXX.sys is driver made for Windows 8, change security_cookie to random value, security_cookie is constant 0x4EE640BB(x32) / 0x32A2DF2D992B(x64) inside file, change only first match ! Place ntoskrn8.sys to X:/Windows/system32/drivers/ folder Compiling: 1) Install Windows 7 DDK v7.1.0 (download from Microsoft site) 1a) Original DDK header files has mistake with definintion of MmAllocateContiguousMemorySpecifyCacheNode, apply fix to two files \WinDDK\Win7\inc\ddk\ntddk.h and \WinDDK\Win7\inc\ddk\wdm.h: replace: #if (NTDDI_VERSION >= NTDDI_WIN2K) typedef ULONG NODE_REQUIREMENT; to: #if (NTDDI_VERSION >= NTDDI_VISTA) typedef ULONG NODE_REQUIREMENT; 2) Download project files to any local folder git clone https://github.com/MovAX0xDEAD/NTOSKRNL_Emu 3) Choose Target OS (XP, 2003, Vista or WIndows 7) for which OS Emu_Extender will be compiled. Keep in mind that depending on the target operating system the way of exporting the functions changes, if a function already exists in the kernel it will be simply redirected without injecting emulation code 4) Run shell: "Start Menu\Programs\Windows Driver Kits\Win7 7600.16385.1\Build Environments\Windows XXX\YYY Free Build Environment" (XXX - target OS, YYY - target CPU) 5) In shell change current directory to local project folder 6) Use shell command BLD to compile project 7) Compiled ntoskrn8.sys will be in ntoskrn8/objfre_XXX_x86/YYY folder STORPORT Windows 7 Emu_Extender This is Library of missing functions for Windows 7' STORPORT.SYS v6.1.7601.23403 to emulate Windows 8' STORPORT.SYS How-To: Compile ntoskrnl Emu_Extender Place storpor8.sys to X:/Windows/system32/drivers/ folder Make corrections to target xxx.sys so that it loads storpor8.sys instead of the original storport.sys Place backported storport.sys from Windows 7 to X:/Windows/system32/drivers/ folder Ported drivers: Windows 7's WDF 1.11 for Windows XP/2003 x32 Last version for Windows XP/2003 is 1.9, but possible to backport 1.11 version: 1) Get files from Windows 7 Updates (KB3125574): WDF01000.SYS v 1.11.9200.20755 WdfLdr.sys v 1.11.9200.16384 2) In WDF01000.SYS replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Recalc checksum If need coexist with original WDF1.9 drivers: 4) Rename WDF01000.SYS->WDF01_W8.SYS, WdfLdr.sys->WdfLdr8.sys 5) In WDF01_W8.SYS replace string WdfLdr.sys to WdfLdr8.sys in import section 6) In WdfLdr8.sys replace unicode string \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d000 to \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d_w8 7) In WdfLdr8.sys replace hex pattern F6 78 1B F6 to F6 EB 1B F6 (x32), ** ** to ** ** (x64) 8) In target driver XXX.sys replace string "WdfLdr.sys" to "WdfLdr8.sys" in import section 9) In .INF of ported driver add creating new service: AddService=WDF01_W8,, WDF.AddService .... [WDF.AddService] DisplayName = "Windows Driver Framework v1.11 for XP/2003" ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\WDF01_W8.SYS LoadOrderGroup = Base Recalc checksum of all edited *.sys Windows 7's Storport.sys for Windows XP x32 Storport was released since Windows 2003, but possible to backport Windows 7 version: 1) Get files from Windows 7 Updates (KB3125574): storport.sys v 6.1.7600.23403 2) In storport.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section, now storport.sys will import all kernel functions only from Emu_Extender 3) Storport uses MSI interrupts, need to force use only legacy/compatible interrupts x32 - replace hex pattern 8B 8E 3C 01 00 00 to B9 00 00 00 00 90 (mov ecx, [esi+13Ch] -> mov ecx, 0) x64 - replace hex pattern 8B 83 C0 01 00 00 to B8 00 00 00 00 90 (mov eax, [rbx+1C0h] -> mov eax, 0) 4) Recalc checksum Windows 7's NVMe driver for Windows XP x32 1) Get files from Windows 7 Updates (KB3125574): stornvme.sys v 6.1.7600.23403 2) MS Win7 NVMe driver require Win7 Storport.sys, use backported one Windows 8's USB3 driver for Windows XP x32 1) Get required files from Windows 8 (KB4534283/4556840, KB2984005, RTM ISO): ucx01000.sys v6.2.9200.22453 usbhub3.sys v6.2.9200.21180 usbxhci.sys v6.2.9200.22099 wpprecorder.sys v6.2.9200.16384 usbd.sys v6.2.9200.20761 from Vista Beta/Longhorn 5456.5: ksecdd.sys v6.0.5456.5 2) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, wpprecorder.sys, usbd.sys change security_cookie to random value 3) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, ksecdd.sys replace string name "ntoskrnl.exe" to "ntoskrn8.sys' in import section 4) Rename ksecdd.sys->ksecd8.sys, usbd.sys->usbd_w8.sys 5) In usbhub3.sys replace string name "ksecdd.sys" to "ksecd8.sys' in import section 6) In usbhub3.sys replace string name "usbd.sys" to "usbd_w8.sys' in import section, 7) recalc checksum Windows 8’s STORAHCI driver for Windows XP x32 STORAHCI driver requires storport.sys from Windows 8, but possible to use storport.sys v6.1.7601.23403 from Windows 7 Storport.sys from Windows 7 more compatible with Windows XP/2003 because it still call required PoStartNextPowerIrp when processing power IRPs. Microsoft removed calls to PoStartNextPowerIrp in Windows 8's storport.sys, without this call Windows XP/2003 kernel cannot finish current power IRP and start next IRP => it generate BSOD (0x0000009F). Also storport.sys from Windows 7 has compatibility mode to allow old XP/2003 kernels write crashdumps through storport based disk drivers. In storport.sys from Windows 8 compatibility mode was removed, writing crashdumps possible only with new kernels. Take attention: Windows 8's STORAHCI + Windows 7's STORPORT may have significal performance drop and high CPU usage, there is no fix yet 1) Get files from Windows 8 (RTM ISO): storahci.sys v 6.2.9200.16384 2) In storahci.sys replace string storport.sys to ntoskrn8.sys in import section 3) Storahci.sys was compiled with Windows 8 DDK's storport.h and writes values to new fields of _PORT_CONFIGURATION_INFORMATION struct, these fields not exist in Windows 7's storport.sys. Need to skip these writes to avoid damaging other structures in memory x32: Replace hex pattern 83 A6 C8 00 00 00 00 to 90 90 90 90 90 90 90 (and dword ptr [esi+0C8h], 0 -> nop) Replace hex pattern 83 8E CC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [esi+0CCh], 3 -> nop) x64:Replace hex pattern 44 89 B7 D8 00 00 00 to 90 90 90 90 90 90 90 (mov [rdi+0D8h], r14d -> nop) Replace hex pattern 83 8F DC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [rdi+0DCh], 3 -> nop) If you want compile storahci from sources (from Windows 8 DDK Samples), comment two lines ConfigInfo->BusResetHoldTime = 0; ConfigInfo->FeatureSupport |= STOR_ADAPTER_FEATURE_STOP_UNIT_DURING_POWER_DOWN; 4) In storahci.sys change security_cookie to random value 5) Recalc checksum Windows 7’s MSAHCI driver for Windows XP x32 1) Get files from Windows 7 Updates(KB3125574): atapi.sys v 6.1.7600.23403 ataport.sys v 6.1.7600.23403 msahci.sys v 6.1.7600.23403 pciidex.sys v 6.1.7600.23403 2) In ataport.sys, pciidex.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Pciidex.sys uses MS Internal/Undocumented HalDispatchTable way to call functions from Kernel/HAL, for Windows XP/2003 need to use compatible variant: x32: Replace hex pattern FF 50 3C to FF 50 40 same in asm code: mov eax, ds:HalDispatchTable ... call dword ptr [eax+3Ch] => call dword ptr [eax+40h] x64: Replace hex pattern FF 50 78 to EB 2A 90 Replace hex pattern at offset +2Ch: CC CC CC CC CC CC CC CC to FF 90 80 00 00 00 EB CF, same in asm code: mov rax, cs:HalDispatchTable ... call qword ptr [rax+78h] => jmp patch orig: mov r10d, eax patch: call qword ptr [eax+80h] jmp orig 4) Recalc checksum 5) MSHDC.INF from Windows 7 conflict with original mshdc.inf from Windows XP/2003. msahci.sys enumerates IDE/SATA channels as "Internal_IDE_Channel" and compatible ID is "*PNP0600". Original mshdc.inf from Windows XP/2003 for compatible Device ID "*PNP0600" will install wrong "Standard IDE/ESDI Hard Disk Controller" driver Intel RSTe (Enterprise/Premium) AHCI/RAID driver 4.7.0.1098 for Windows XP/2003 Intel RST AHCI/RAID drivers (any version, last compatible is 16.8.3) for Windows XP/2003 These drivers require storport.sys from Windows 7, use backported version. 1) In file iaStorA.sys/iaStorAC.sys/iaStorAVC.sys replace string “ntoskrnl.exe” to “ntoskrn8.sys” in import section (do not change second string “NTOSKRNL.exe”) now these *.sys will import kernel functions only from Emu_Extender 3) Recalc checksum Implemented Func List v60: _chkstk _i64toa_s _i64tow_s _itoa_s _itow_s _ltoa_s _ltow_s _makepath_s _snprintf_s _snscanf_s _snwprintf_s _snwscanf_s _splitpath_s _strnset_s _strset_s _strtoui64 _swprintf _ui64toa_s _ui64tow_s _ultoa_s _ultow_s _vsnprintf_s _vsnwprintf_s _vswprintf _wcsnset_s _wcsset_s _wmakepath_s _wsplitpath_s _wtoi _wtol DbgkLkmdRegisterCallback EmClientQueryRuleState EtwActivityIdControl EtwEventEnabled EtwProviderEnabled EtwRegister EtwRegisterClassicProvider EtwUnregister EtwWrite EtwWriteString EtwWriteTransfer ExAcquireRundownProtectionCacheAware ExAcquireRundownProtectionCacheAwareEx ExAllocateCacheAwareRundownProtection ExDeleteLookasideListEx ExEnterCriticalRegionAndAcquireFastMutexUnsafe ExEnterCriticalRegionAndAcquireResourceExclusive ExEnterCriticalRegionAndAcquireResourceShared ExEnterPriorityRegionAndAcquireResourceExclusive ExEnterPriorityRegionAndAcquireResourceShared ExFreeCacheAwareRundownProtection ExfReleasePushLockShared ExfTryToWakePushLock ExGetFirmwareEnvironmentVariable ExInitializeLookasideListEx ExInitializeRundownProtectionCacheAware ExReInitializeRundownProtectionCacheAware ExReleaseFastMutexUnsafeAndLeaveCriticalRegion ExReleaseResourceAndLeaveCriticalRegion ExReleaseResourceAndLeavePriorityRegion ExReleaseRundownProtectionCacheAware ExReleaseRundownProtectionCacheAwareEx ExRundownCompletedCacheAware ExSetFirmwareEnvironmentVariable ExSizeOfRundownProtectionCacheAware ExWaitForRundownProtectionReleaseCacheAware IoAllocateSfioStreamIdentifier IoConnectInterruptEx IoDisconnectInterruptEx IoFreeSfioStreamIdentifier IoGetActivityIdIrp IoGetAffinityInterrupt IoGetDevicePropertyData IoGetIoPriorityHint IoGetSfioStreamIdentifier IoInitializeWorkItem IoQueueWorkItemEx IoSetActivityIdIrp IoSetDevicePropertyData IoSizeofWorkItem IoUninitializeWorkItem IoUnregisterPlugPlayNotificationEx KdRefreshDebuggerNotPresent KeAcquireGuardedMutex KeAcquireGuardedMutexUnsafe KeAlertThread KeAreAllApcsDisabled KeEnterGuardedRegion KeExpandKernelStackAndCallout KeGetCurrentNodeNumber KeGetCurrentProcessorNumberEx KeGetProcessorIndexFromNumber KeGetProcessorNumberFromIndex KeInitializeGuardedMutex KeInvalidateAllCaches KeInvalidateRangeAllCaches KeLeaveGuardedRegion KeQueryActiveGroupCount KeQueryActiveProcessorCount KeQueryActiveProcessorCountEx KeQueryDpcWatchdogInformation KeQueryGroupAffinity KeQueryHighestNodeNumber KeQueryLogicalProcessorRelationship KeQueryMaximumGroupCount KeQueryMaximumProcessorCount KeQueryMaximumProcessorCountEx KeQueryNodeActiveAffinity KeReleaseGuardedMutex KeReleaseGuardedMutexUnsafe KeRevertToUserAffinityThreadEx KeRevertToUserGroupAffinityThread KeSetActualBasePriorityThread KeSetCoalescableTimer KeSetSystemAffinityThreadEx KeSetSystemGroupAffinityThread KeSetTargetProcessorDpcEx KeTestAlertThread KeTryToAcquireGuardedMutex LdrResFindResource LdrResFindResourceDirectory LpcReplyWaitReplyPort LpcRequestWaitReplyPortEx LpcSendWaitReceivePort memcpy_s memmove_s MmAllocateContiguousMemorySpecifyCacheNode MmAllocateContiguousNodeMemory ObDeleteCapturedInsertInfo ObfDereferenceObjectWithTag ObfReferenceObjectWithTag ObGetObjectType ObQueryNameInfo PcwAddInstance PcwCloseInstance PcwCreateInstance PcwRegister PcwUnregister PoDisableSleepStates PoEndDeviceBusy PoGetSystemWake PoReenableSleepStates PoRegisterPowerSettingCallback PoSetDeviceBusyEx PoSetSystemWake PoStartDeviceBusy PoUnregisterPowerSettingCallback PoUserShutdownInitiated PsAcquireProcessExitSynchronization PsEnterPriorityRegion PsGetCurrentProcessWin32Process PsGetCurrentThreadProcess PsGetCurrentThreadProcessId PsGetCurrentThreadTeb PsGetCurrentThreadWin32Thread PsGetCurrentThreadWin32ThreadAndEnterCriticalRegion PsGetProcessSessionIdEx PsIsProtectedProcess PsIsSystemProcess PsLeavePriorityRegion PsReleaseProcessExitSynchronization PsSetCreateProcessNotifyRoutineEx RtlCheckPortableOperatingSystem RtlGetIntegerAtom RtlGetThreadLangIdByIndex RtlIsNtDdiVersionAvailable RtlQueryElevationFlags RtlQueryRegistryValuesEx RtlSetPortableOperatingSystem SeReportSecurityEventWithSubCategory SeSetAuditParameter SeSetAuthorizationCallbacks sprintf_s sscanf_s strcat_s strcpy_s strncat_s strncpy_s strnlen strtok_s swprintf_s swscanf_s vsprintf_s vswprintf_s wcscat_s wcscpy_s wcsncat_s wcsncpy_s wcsnlen wcstoul ZwAllocateLocallyUniqueId ZwAlpcConnectPort ZwAlpcSendWaitReceivePort ZwQueryLicenseValue ZwQueryVirtualMemory Download Sources https://github.com/MovAX0xDEAD/NTOSKRNL_Emu

But this is not the case,, it seems like specifically the suggested program does not (cannot) see the way the .dll is checked/accessed (which is seemingly non-standard), if you prefer, it is more like the usefulness of a bycicle to a fish: https://www.fishonabike.com/guinness.htm jaclaz

I never said I didn't understand the situation. I don't mind paying money for something. But I do expect the person selling it to be honest about it. I have absolutely no idea if he's honest about it. I don't really feel you really try to understand what I'm saying. "I have donated more than once but I also wait patiently for the updates without plastering complaints all over the forum here" I don't "plaster complaints all over the forum" either. I've been mostly (trying) to help people out and some questions/comments here and there. But yeah, thanks a lot for your reply. I guess I'm just overthinking things or something. I'm still waiting patiently. Checking the forum from time to time.

You are entitled to your opinion and no the majority of Windows users don't disagree with me...rubbish...it's your opinion - but don't include everyone else because you haven't a clue about what you are stating. Linux was never good enough for Microsoft...all of a sudden things are different?! Linux has a far better support and development network than Microsoft ever will...and because you say you haven't much experience of Linux...then my advice...get some before having an opinion...

I have now fixed the import calls and added K32EmptyWorkingSet. So about 26 more functions to go in kernel32! OBS Studio 19.2.0 is mostly working now, but there are a few missing functions in MFPlat.dll (Media Foundation Platform), like MFTEnumEx (used to find video/audio decoders) and MFCreateMFByteStreamOnStream. While it picks up on audio, it doesn't record or show video and creates tiny (corrupt) files. Or it may be because it forces a D3D11 renderer and my DX10 native GPU doesn't seem to work very well with DX11 (Cities: Skylines is unplayably glitchy in D3D11 mode on Vista and 7 but fine in D3D9 mode on XP x64). I think that the media foundation extensions will be fun, as I may even introduce the functions from Windows 8 as opposed to just the ones new to 7. That would mean adding stuff like Direct3D 11-based video APIs. Though adding DX11.1+ features will be pointless if the drivers available for Vista can't use them. And getting WDDM 1.1+ drivers on Vista is going to be one difficult undertaking, but probably easier than porting WDDM 1.0 drivers to XDDM (Windows 2000 Display Driver Model). And I've found another limitation of LOCAL files. Programs don't like being debugged when redirection is taking place to files within folders; they throw a fault in StackHash_**** when trying to launch them through Dependency Walker. But if the same file is loaded from system32 as opposed to the program directory, with no redirection taking place, the program works (as well as possible) through Dependency Walker. So I thought about .manifest files, which give you the option to redirect only the files specified within them. Here is an example of the contents of a manifest file used for DLL redirection: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" name="redirector" type="win32" /> <file name="kernel32.dll"> </file> </assembly> But it appears that manifest files don't seem to help much in that regard. So I guess you will have to replace your system files with mine if you're planning on debugging programs using my files. Once I get a wide array of programs working stable, I hope that you do one of your excellent videos about the kernel's capabilities. You create some great promotional tools for Vista, and this one will explore some uncharted territory for the OS. On one last note, this isn't the only new kernel extension project that helps Vista users out: The tutorial specifically mentions building for x86, but I built it in the Vista x64 build environment in the Windows 7 DDK, so it could help with certain classes of drivers. Will it help for modern GPU drivers? Not really. NVMe and USB 3? Sure.

Probably not because for years, people have been clamoring for transparent title bars from MS, and even after getting thousands of upvotes on several posts relating to adding acrylic title bars to Windows on the feedback hub, there is no sign that this is even being actively worked on.

Wow! Am I dreaming?! Vista Extended Kernel is a reality?! Thank you, @win32 for putting work into this project and bringing it to fruition, and creating this tutorial. This is something that has been discussed & yearned for among those of us "old-timers" in the Vista community as early back as 2013/2014, and the closest thing we ever got was @smeezekitty's proxy stub DLL wrappers for Adobe Reader DC & Catalyst Omega, but unfortunately he has been inactive since 2016 I never thought anyone would ever come forward with a full-blown extended kernel project. This is very exciting & promising as I had planned to stick with Windows Vista indefinitely, but worried for the future as software support (namely browsers) has continued to diminish. I'm not much experienced with any kind of coding, but if I can be of help in any way, do let me know. I apologize to everyone here in the Vista community for being so inactive lately. Being an "essential" employee (letter carrier for USPS) during a pandemic is not easy! Package volume is through the roof since no one (understandably) wants to get out Hope everyone here is staying safe.

Yes. I just need to do about ten more patches of call near ptr to call cs: in the nine existing functions, and then I'll be adding more. These are other missing ones that I've found to be called by programs: GetNumaNodeProcessorMaskEx GetCurrentPackageId GetSystemTimePreciseAsFileTime plus their dependencies and sister functions Those are going on the list along with the other unimplemented K32 functions as well as TryAcquireSRWLockShared (not sure why I shelved it earlier - perhaps because it's really a ntdll function but it doesn't matter since nothing really seems to call them directly from ntdll so it can go into kernel32, like BWC has done). Anyway, I really like these x64 dlls. MS gets to do its own thing in its own code section, while I can just make a section for myself and move the export table to its own section and things are good. All of the existing functionality of Vista is retained and not a single beat is skipped. And if you choose not to replace your existing kernel32.dll and just use the modified one on a per-program basis using .exe.local redirectors, you will be preventing the direct execution of malicious executables requiring W7+ functions. I'm also thinking about compatibility shims - One-Core-API expanded the amount of shims available in XP to include OSes like Vista/7/8.1/10. I think that I need something like that to get some installers to run since that seems to go above and beyond what Application Verifier can provide.

My reply is a 2 month old bump... but this, necessarily, is what caused the problem. Laziness, ease of throwing things together, slapping a bunch of ads together, internet becoming more of a profitable means of distribution = easy money for people. The modern internet doesn't seem to stick out individually anymore though, it's all bland, and I guess it's down to ease of just throwing together things that way. I guess that also partly influenced (or vice versa) why a lot of big websites have over the past eight years or so removed many 'custom profiles' (making them more generic), and overall deprecating things that give a sense of community unless it is somehow profitable to do so for businesses as well. My biggest concern is accessibility, which is essentially thrown out of the window for slower-developing countries with lesser access to fast-speed/always-on Internet; oh, and small-screen devices, due to the more-than-useless cookie consent banners the EU imposed on the world in 2012, that can't even dismiss the stupid prompts without messing with the zoom settings.

One already has a choice..Run Linux or Windows...Linux should never be connected to anything to do with Microsoft. Windows is crap and Linux is much supperior...end of story...😀

We have absolutely no idea how long it takes. It could take a full week or it could take 12 hours. We have no idea. This is what I mean with speculation. Did he ever share any info regarding what it takes to update? How big of a chance is there even that this can cause bugs? And if a lot of bugs can be there does he have a very solid way of fixing these with some kind of debugging software perhaps? And having an application without bugs is pretty logical yes. I don't see how that changes anything in this particular situation. We still don't know how much testing is actually done each update. Also, the application is not free. If you can pay for it how is it free? Unless you can pay for the application and your payment changes nothing. You would have the exact same feature set with no downsides. That's what we call an donation. This is clearly a trial/demo. Anyway, I appreciate what BigMuscle is doing because I think this isn't an easy task. He is probably doing this for himself and a small group of people. At least I think so. Like I said, I'm speculating just as much as all of you. I just wanted to get this off my chest. I understand most of the people present on this section of the forum will probably disagree with me or think I don't appreciate what he has created. There is no need for me to make everyone uncomfortable (hopefully I didn't) for a long period of time with replies going back and forth. I really don't want that. The world is already in a full epidemic at the moment. So I just wanted to share what I think, considering this thread was somewhat steering towards the topic. So yeah, be safe and sorry for waltzing in here with my skepticism. I'm just a user like all of you and I can be a bit harsh with what I say. Good day everyone! EDIT: Thinking about it a bit more, I think I might've been a bit too harsh/distrustful. See it as simple food for thought for now, or something. I'm probably overthinking things.

Hello I am French I am a fan of Windows Longhorn and Windows Vista RTM here is my config

I added an additional list of malware content: urlhaus-filter (Online Domains) The 3 predefined malware lists don't seem very efficient. "Malware Domain List" also blocks links from 2017 that have been inactive for some time. "Malware domains" can easily be replaced by DNS blocking. I deleted the "Spam404" list (Phishing) because many links are blocked by DNS or inactive. I also deleted the "NoCoin Filter List".

Not sure how you think he complained. He said replacing dll files with older files will brick a system. That's not complaining. That's letting people know the work around is no longer working.