Leaderboard

@Dave-H and @Dylan Cruz I've fixed it! Found an easy way to fix Office 2010 and not break TLS updates. Get KB3081320 from WU Catalog, extract it and copy dssenh.dll to C:\Program Files\Microsoft Office\Office14. That's it.

it would be the same on an x64 system. The only thing that really changes on x64 is that x86 components come under a "Wow6432Node" key.

BTW @roytam1 If you are wondering about shellservice and nsis installer code.. I am gonna be upgrading that modifying the copy from Pale Moon which was modified from Basilisk when Pale Moon was ported to UXP from Tycho. The technical reason is simply this.. The Suite Shellservice is not very appropriate for a standalone web client and over the years the SeaMonkey people have mangled it pretty badly and pieces of it are ancient. Basically getting a fresh copy that is geared to JUST a web client will improve matters greatly. The reason the nsis scripting is involved is because on Windows the shellservice needs to issue commands to an external application that can elevate and Mozilla shared routines in nsis scripting to produce the helper.exe which serves during install as well as commands issued by shellservice. Those two items need to be consistent. But yeah until I get it replaced you can just revert that. However, I suggest once it is replaced and verified you should switch it to that for best results.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200808-57e81f0-uxp-b5762c6c2-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200808-57e81f0-uxp-b5762c6c2-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200808-57e81f0-uxp-b5762c6c2-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.10.1a1.win32-git-20200808-5f05a0799-uxp-b5762c6c2-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.1a1.win64-git-20200808-5f05a0799-uxp-b5762c6c2-xpmod.7z Official UXP changes since my last build: - Issue #1621 - Part 1: CSSEditUtils should use atom for CSS property if possible. (baa4b609d) - Issue #1621 - Part 2: Implement nsIAtom version of SetAttribute/RemoveAttribute/CloneAttirubte. (1c0c7cf58) - Issue #1621 - Part 3: Use nsIAtom to change attirbute if possible. (1115c63bf) - Issue #1621 - Part 4: Check whether node can be splited. (5f6ecd756) - Issue #1619 - Convert Intrinsic Ratio to Float (232f987cf) - Use an alt script to properly determine the OSX SDK version (c3ec6c613) - Add license header to media/webrtc/trunk/build/mac/find_sdk_uxp.py (02bd56c44) - Issue #1619 - Missing Dimension Computation (e664d4369) - Issue #1619 - Add Vertical Writing Testcase (ba0a2e796) - Issue #1619 - Nits Picked (a90b8d98e) - Merge pull request #1622 from RealityRipple/master (2e1c5dafc) - [js] Try to catch bad pointers for GC and bail if not valid. (8d38e3575) - Issue #1625 - Allow MailNews Oauth2 support to be configured in confvars.sh (7c6d822be) - Merge pull request #1623 from g4jc/libeditor_patch (267d32f4f) - Issue #1628 - Remove redundant PREF_EM_UPDATE_BACKGROUND_URL (d357eec56) - Pref and disable getRootNode() (b5762c6c2) Official Basilisk changes since my last build: - Update Back-end branch pointer (c15535d) - Issue MoonchildProductions/UXP#1628 - Remove extensions.update.background.url from preferences (57e81f0) Official Pale-Moon changes since my last build: - Update back-end branch pointer (2762ee9d5) - Issue MoonchildProductions/UXP#1628 - Remove extensions.update.background.url from preferences (5f05a0799) My changes since my last build: - Revert UXP issue 1628 related changes. (35f288dc4)

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

Welcome to Windows XP Service Pack 4 (Unofficial). Windows XP SP4 (Service Pack 4) is a cumulative update rollup for Windows XP. Windows XP SP4 Final is now available! Windows XP SP4 can installed on any version of Windows XP with SP1 or later installed or slipstreamed into any Windows XP installation source (except for Embedded versions). It includes all updated components and hotfixes for Windows XP in a single, convenient package. Except for the SP4 package installer main executable (update.exe) and a cosmetic resource modification sysdm.cpl no other binary file has been modified, everything is original from Microsoft Corporation. Microsoft .NET Frameworks 4.0, 3.5, 1.1, 1.0 are included in this package. .NET Framework 1.0 will be installed only with Tablet PC Edition or Media Center Edition (Upgrade only). .NET Framework 4.0 is disabled by default. It's possible to split the slipstreamed installation source into two 650 MB CD-ROMs, which can be essential for older computers. You can also create 6 Bootable Floppy Disks to install Windows XP on older systems which cannot boot from CD-ROM. Furthermore, Windows XP SP4 includes security enhancements that address issues not fixed by Microsoft Updates. It also includes performance tweaks that should make your PC run blazingly fast. NOTE: Before installing SP4 on a system with many post-SP3 updates installed, follow the steps described here (do not restart your PC after applying these steps, just run the SP4 installer and then reboot): http://www.rarst.net/software/failed-install-catalog-files/ This will prevent a common error message: "Failed to install catalog files" Although SP4 installer takes steps to automatically delete these files, it may require manual intervention in some cases. Download at official Internet Archive repo: https://archive.org/details/xp-unofficial-sp4-jan2022_20220113 View contents of ryanvm-archive-xpsp4-posts.7z on the Internet Archive download location for additional information. (Current version: Version 3.1b Released on 08 March 2016 23:00:00 UTC). Enjoy Windows XP Service Pack 4. 1 - UPDATE [June 7, 2019]: Post-SP4 Update Pack released! This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net. 2 - UPDATE - 15 OCT 2018: For novice users that do not want to wait for 20-30 minutes after installing XP SP4 AND rebooting For all .NET haters... A NEW RELEASE OF UNOFFICIAL SP4 3.1B WITHOUT .NET FRAMEWORK This release will not install .NET Framework in both live and slipstreamed install, unless: - Media Center Edition is used -> .NET Framework 1.1 SP1 is installed - Tablet PC Edition is used -> .NET Framework 1.0 SP3 is installed Users can still install .NET FWs of their choice from the Add/Remove Components wizard in Control Panel This alternative SP4 release is called: WindowsXP-USP4-v3.1b-NODOTNET-x86-ENU.exe In addition, XP SP4 OEM Preinstallation Kit ISOs with SCSI drivers, and an updated MUI ISO have been released! 3 - IMPORTANT NOTICE FOR XP SP4 USERS [08/03/2016]: Microsoft has changed its WU update detection strategy. The following key must be removed to continue receiving automatic updates from WU: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded Use the sp4_march16_wufix.reg found inside the respective zip file at my Google Drive in order to automate the process. Version 3.1a users don't need to do anything more than that. A new v3.1b version has been released with this change, just for new installs. No other updates have been added.

MS has released updates adding TLS 1.1/1.2 to XP and IE8. It lacks some encryption methods, but most sites using TLS 1.2 open fine.

Schwups, I understand your point here but I'm not inclined to do that for a number of reasons: first is that all I know/figured out has now been written and it is within the last 4/5 pages of this thread, second is that there is no foundation on which I can write a guide and by this I mean that running Burp requires a properly updated KernelEx which is even more complicated to get to, it was quite easy to sort out Dave-H only because he had followed regularly up to a point and only missed an update of the psapi auxilliary dll to his updated KernelEx, third, I don't believe there are many newbies if any at all and all this should be good enough for the handful who follows these 9x topics at least semi-regularly.

A while ago I did some google search about WUMT. The developer of the tool is said to be elusive and avoids publicity. The Russian forum mentioned above seems to be the original source of WUMT and the thread on My Digital Life followed. There are two verions of WUMT: 20.12.2016 - supports XP -> Win10 07.01.2020 - supports Win10 only Major Geeks replaced v20.12.2016 with v07.01.2020 early this year and does not have the older version available for download any more. Windows Update Offline Scan File wsusscn2.cab is updated from time to time and includes lists of all available updates for different versions of Windows. I could not figure out how often it is updated and which OSes are actually supported. I used it with XP, POSReady 2009 and Windows Embedded Standard 7. Here are all relevant links and checksums: v20.12.2016 wumt.zip MD5: 200B3B2198F32AFC6FBF2D5B6110C5CC v07.01.2020 wumt.zip MD5: 4B4BB34ADC4376E6F6DA6961DC59FAB3 WUMT - original source: http://gallery.ru-board.com/topic.cgi?forum=5&bm=1&topic=48142#2 WUMT - primary thread in English: https://forums.mydigitallife.net/threads/windows-update-minitool.64939/ Official web page of wsusscn2.cab: https://support.microsoft.com/en-us/help/926464/a-new-version-of-the-windows-update-offline-scan-file-wsusscn2-cab-is

Dave, your suspicions are correct. Installed the original SP3 release of XP, then Office 2010 with all updates and replaced MSO.DLL with the one from KB4092483. Saving an encrypted Word document (docx) does work. On the other hand, installing Office 2010 with no updates on a fully patched (including POSReady updates) XP SP3 installation, gives the same error when saving a password protected docx. What I've tried so far: - remove POSReady key, does NOT work - applied revoked certs update on original SP3, does NOT break encryption - applied root certs update on original SP3, does NOT break encryption I strongly believe that Microsoft broke encryption support on POSReady updates as Office is not supported on that SKU. Extending XP support for free with no ill effects? No, there is no free lunch. Someone with update lists need test XP SP3 with official updates up to April 2014 and test encryption on Office 2010. Then install POSReady updates (one by one ) to identify which one breaks Office.

For the more observant among you, you might've noticed that @Dylan Cruz 's last screengrab contains one additional IE9 cipher suite [TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13)] that is absent on my IE9 SSL Labs Client Test! In fact, on a TLS 1.0+1.1+1.2 enabled Vista SP2 machine, IE9 supports the below twelve variations of cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Forward Secrecy 128 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Forward Secrecy 256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Forward Secrecy 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Forward Secrecy 256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x32) Forward Secrecy(2) 128 TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x38) Forward Secrecy(2) 256 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13) WEAK 112 TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK 256 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK 112 TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 (2) Cannot be used for Forward Secrecy because they require DSA keys, which are effectively limited to 1024 bits. At some point, I had removed support for half of them, deemed to be extremely WEAK/insecure: Removed: *TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128 (TLS1.1) *TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK 256 (TLS1.1) *TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK 112 (TLS1.2) *TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13) WEAK 112 *TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 *TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 which currently leaves me with TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Forward Secrecy 128 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Forward Secrecy 256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Forward Secrecy 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Forward Secrecy 256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x32) Forward Secrecy(2) 128 TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x38) Forward Secrecy(2) 256 NB: The last two do not support FS, so I might remove them, too... PS: On my 32-bit system I used Disable_RSA_Ciphers_RC4-128-128_3DES-168.reg : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\PKCS] "Enabled"=dword:00000000 A computer restart is needed before these changes take effect! Reference: https://support.microsoft.com/en-us/help/245030/how-to-restrict-the-use-of-certain-cryptographic-algorithms-and-protocols

The Protocol Support section of the SSL Client Test available in browserleaks.com also fails for me here in IE9 32-bit: ... while, at the same time, the Handshake section is displayed correctly: Perhaps they're using some CSS/JS code in the first failing section that the deprecated IE9 rendering engine can't cope with... (?) For IE9 specifically, you may want to use the SSL Labs Client Test, https://www.ssllabs.com/ssltest/viewMyClient.html :

WUMT v07.01.2020 supposedly only launches under Win10: (It doesn't on Vista SP2 32-bit here ... ) ... Which is exactly? FTR, I got my copy of Windows Update MiniTool v20.12.2016 from our Russian friends! https://forums.mydigitallife.net/

Your IE9 version number depends on which cumulative security update for IE9 is installed. The last cumulative security update with a dual signature was KB4507434. (VistaLover wasn’t using that one in July 2017 because it wasn’t released until July 2019.) For those who have installed SHA-2 support, the highest possible version of IE9 remains a cutting-edge question. Your latest and longest post seems to be about the reg files that were created by greenhillmaniac, who has never posted in this thread. It is possible to scrutinize the changes in a reg file without running it. I have looked at the reg files (in fact once offered some input regarding the x64 version), and recall some arguably superfluous changes that I interpreted as being for the sake of security (e.g. having SSL enabled has been unwise for years). If anyone running Vista x64 would like to manually edit their registry pursuant to TLS 1.1 and 1.2, see this post.

mse downloads definition updates after adding sha2 support.

If you have already installed a number of Server 2008 updates, then you probably have KB4056564, which superseded KB4019276 as first noted in a June 22, 2018 post above. Otherwise, you might have downloaded a patch with incorrect bitness or for Itanium-based systems.

@roytam1 : Can you please NOT implement upstream issue #1628 https://github.com/MoonchildProductions/UXP/issues/1628 in your custom UXP branch? I don't know about New Moon 28, but in Serpent 52.9.0 we do still support WebExtensions installable from/updatable by AMO, and the use of a modified value for the extensions.update.background.url pref is a viable way to keep checking for WE updates (from AMO), while the standard extensions.update.url pref can be left pointing at the Basilisk extension repository (or, possibly, vice versa; point the main URL to AMO and the background one to addons.basilisk-browser.org...). FWIW, in my copy of Serpent 52.9.0 I have: extensions.update.background.url;https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=52.9&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE% Thanks in advance, take good care!

Here's my final rundown, with notes: Seems like everything installed! I did a brief random sampling trying to hit all the bases and it seems they are all there in Add/Remove Programs +Show Updates. Beats me why nLite was incapable of making it work. It literally errored out on all of them. DISM isn't in XP so I'm not sure how else to slipstream these post-SP4 updates. Waiting for an SP5, hopefully... Post-SP4 updates list Part 1: Normal updates (only?) Installing KB3126587 Installing KB3139398 Installing KB3139914 Installing KB3140709 Installing KB3149090 Installing KB3161949 Installing KB3170455 Installing KB3183431 Installing KB3185911 Installing KB3196718 Installing KB3197835 Installing KB3198510 Installing KB4012583 Installing KB4012584 Installing KB4012598 (WannaCry) Installing KB4014652 Installing KB4014794 Installing KB4018466 Installing KB4019204 Installing KB4019276 Installing KB4022747 Installing KB4024323 Installing KB4024402 Installing KB4025218 Installing KB4025409 Installing KB4025497 Installing KB4034775 Installing KB4039384 Installing KB4041995 Installing KB4047211 Installing KB4052303 Installing KB4056564 Installing KB4056941 Installing KB4089082 Installing KB4089175 Installing KB4089453 Installing KB4089694 Installing KB4091756 Installing KB4101477 Installing KB4130957 Installing KB4291391 Installing KB4294413 Installing KB4457163 Installing KB4458000 Installing KB4458001 Installing KB4458006 Installing KB4458318 Installing KB4459091 Installing KB4462935 Installing KB4463103 Installing KB4463573 Installing KB4467689 Installing KB4467770 Installing KB4470118 Installing KB4473077 Installing KB4486463 Installing KB4486465 (Thought to be problematic, as part of post-SP4 update pack, but seems not to be?) Installing KB4486468 Installing KB4486536 Installing KB4486538 Installing KB4487990 Installing KB4489493 Installing KB4489973 Installing KB4489977 Installing KB4490228 Installing KB4490501 Installing KB4491443 Installing KB4493341 Installing KB4493563 Installing KB4493790 Installing KB4493793 Installing KB4493794 Installing KB4493795 Installing KB4493796 Installing KB4493797 Installing KB4493927 Installing KB4494059 Installing KB4494528 Installing KB4495022 Installing KB4500331 (2019 RDP patch) == Press any key to restart == Part 2: POS updates only KB2926765 KB3126587 KB4018556-v2 KB4022746 KB4025398 KB4034044 KB4230467 KB4293928 KB4338381 KB4339284 KB4339291 KB4339854 KB4340937 KB4458003 KB4493435-IE8

YouTube seems to work more or less fine in New Moon 28 and Firefox 52.9 ESR on Windows 2000 with Extended Kernel. Presumably, would work in XP, too.

Youtube-dl

For now, wumt and wsusscn2.cab is still able to search, download and install updates. Probably is a good idea to backup wsusscn2.cab. Microsoft might remember to delete older updates at anytime from now. (Top: vista sp2 vanilla, Bottom: xp sp3 + posready)

I'm slightly shocked that invidious goes down the tubes now too :-( And keepvid is unusable too again (or needs stronger JS / younger browsers) Choices get slimmer and slimmer... all that's good gets destroyed since decades, what a shame. (offtopic: and just discovered, the pageadviser domain is up for sale too) Tested a bit yesterday, for me this seems the last remaining *working* download service - anyone know others? (xxxxx = video ID) https://bitdownloader.com/download?video=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dxxxxxxxxxx Perhaps ruclip.com, but no chance without JS either. Best chance IMO are userscripts which extract the full download-URLs from the video page source. Which is possible from all layouts, even polymer if the page shows only empty space and gray rectangles. Luckily that's what I'm using too. The prob is, Google must allow this, or won't work. At the moment they still do, for those videos which officially have permission to be downloaded. But others (like new, protected music videos) are not downloadable/viewable this way at all. Am afraid it's only a matter of time until GoogleGod will decide he wants to block ALL downloads, which will be very easy. They could simply obfuscate all download URLs as they already do with protected videos, or worse, if visitors have JS blocked or don't fulfill other tracking requirements, not send them any URLs at all. Without a download service and neither a userscript, the last resort could be to try and manually extract the page source: Hit CTRL+U and search in html source for: "itag\":18, to find the download URL for mp4-video in 360p quality. The URL is about 3000 letters long (!!) and ends shortly before "mimeType" Other sizes: 22 = hd720p 18 = medium 360p 36 = small 144 (actually 320x240, save as *.3gp, only available with a MOBILE useragent) .

Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.

Longhorn build 5456.5 is on WinWorld.

Way to do, @Mov AX, 0xDEAD!

Thanks a lot! BTW, you're right: it's not it. I guess the best way would be to serch by date 1st, starting not earlier than July the 1st... he sure edited that source along the way, so probably the last version was modified and compiled after July the 17th or around it... I have no hurry at all, do take your time, and thanks for your help! You do rock!

Well, since you kindly located the TRIM sources for @xrayer, I do have a request, too, in case you can find a little time to spare: on July the 17th, RLoew reported he had found out the SCSI commands for changing the apparent sector size of WDC external USB disks (in the thread quoted below, from the quoted post onwards)... So, whatever source code and compiled programs related to this must be from not more than a couple of days before his initial post about it, and probably were one o the last things he worked on. I'd love to have a look on whatever you can find, either in source form, notes or test executables, in case any can be found. Sorry to bother, but it's a subject we all were just starting to pursue, and his were the 1st applicable results, so it'd be a great help to get them. Thanks in advance!

Alright, that's cool! I'll also make sure to include a link to rloewelectronics.com when you get that up.

You are welcome to put something up. I just got the rloewelectronics.com domain that I'll put everything on as I sort it out. Reading your post, I think he had given me a copy of Borland's Turbo C compiler at some point. It does seem like he had some sort of custom handling of his includes.

Wow, this is awesome! Thank you very much for this. It's certainly appreciated especially during this hard time for you. Don't feel obligated to rush things, take all the time you need. We're all just so glad that his "presence" didn't just go cold and nobody knows what happened to him so thank you for continuing to login and update us on things. I'm hoping that you've been able to find some sort of comfort in this difficult time considering tomorrow will be a month since your dad's passing. It's still hard on some of us, myself included, but we're getting through it. I'm just sorry I never got to talk to him and know him on more of a personal level.

Thank you, I've been in touch with @LoneCrusader regarding his cotnact with my father. I appreciate what you've done with my dad's account. I have found some source code, lots of it, so I know some of it isn't related to his patches. I'm going to make that stuff available too once I actually have some free time (my life was already busy before all of this). @LoneCrusader mentioned to me that he might have been using a custom compiler which I am unaware of at the moment so it may not just compile nicely. But, I've attached a few of the TRIM named files (and what look like dependencies he had) that I have. I don't know if these are the most recent or even if they are the right ones! BLK13EX.C TRIMCHK.C TRIMCMD.C DISKPORT.C TRIM.C DRIVE.C IDENTIFY.C GETNUM.C

he will be missed. He helped so many people around the world during his lifetime, and he will always be remembered

He was a amazing man , Of course a good friend . It is honor for me that i once worked with him in some project and learned many thing from him. He was pioneer in patching OSes beyond their limit . He was always straight forward which is rare in today's engineer . I cannot say anything , i am crying . Heck even i am so late , as i was offline for long . We will definitely miss him. RIP

I come back after a bit of absence and what do I find.... this is really upsetting, RIP

Wow, that is quite a timeline you have provided here. Let me first start out by saying thank you ever so much for posting this and giving those that "knew" him some closure. I know @LoneCrusader will probably appreciate seeing this post as well because he and your dad kept in contact a lot and worked on projects together. I'm glad it also helped to get it off your chest as well, so it benefited all of us in the end. I still feel very sad over the loss and in time we will all heal but it sounds like he was quite a trooper through the whole thing but unfortunately just wasn't strong enough to come through. But some of us truly liked your father and he was always welcome here. As a small token of our gratitude, we promoted his account that you're using to the patrons group which is reserved for those who have had a special impact here or retired staff members. We know it's not much but it's all we can really offer along with our most sincere condolences. While you may or may not have much use being here, please be aware that you're certainly most welcome in the community, even if you just want to talk to some of us who were close to your dad. Not a lot of people would have done what you did but I know myself and others will be more at peace with your dad's untimely passing. Again, thank you ever so much for the update!

Just to make you aware: The Vogons Community was able to provide some of the software sold on rloew's website in the past. It has been archived on archive.org so it doesn't get lost: https://archive.org/search.php?query=creator%3A%22Rudolph+R.+Loew%22 If you have bought some software still missing there, you can help extending that library. Just make sure to fill the creator field with "Rudolph R. Loew" so it gets added to that list. I wanted to create a collection, but that's only possible with a minimum of 50 items. So we'll have to make due by going with the creator name.

Very sad to hear this. I didn't use his software, but I always respected his knowledge and experience. Rest in peace, Rudolph.

My sincerest condolences. He was one of MSFN's most talented individuals. I'm still in awe about how he was able to do so much for the Windows 9x series of OSes. He will be missed greatly.

I have bought him many programs my projects over the years. I last contacted him two days after his death to buy a large hard drives patch. At the same time, I was asking for advice a few problems my new win 98SE installation, I wondered why he was not responding and his website was down as well. I then already sense that something bad was happened. I got confirmation when I read https://kraussfuneralhome.com/tribute/details/858/Rudolph-Loew/obituary.html that he is dead. He was genius and a big loss DOS/ Win9X community. R.I.P Rudolph.

He did a lot for the 9x community, It's a huge loss. I heard about this little over a week ago but I never bought anything from him or did I know him more or less than other people around here. Ya we don't know anything about his estate, or if anyone inherited his intellectual property. We don't know if his programs and drivers will continue to be available or become abandonware, with no way to acquire going forward. Id say it's probably better to give it some time and see if his work is taken over by new management. if not than everything he did will be lost forever, unless its archived for the public. I did archive his entire website last weekend in the wayback machine, but most of his stuff wasn't free.

Truly sad. RIP Rloew.

Rest in peace, Legend Rloew. You were a Windows 9x god. For historical purposes, here is a recent archive of his web site, dated 12th August 2019. http://web.archive.org/web/20190812081523/http://rloew.x10host.com/

This is really sad, I recognized that name anywhere when it came to 9x enhancements. Rest in peace.

This is extremely sad news indeed, I'm surprised more haven't replied to this thread already. He was certainly a genius when it came to figuring these things out. He'll always be a well respected developer and patron here. RIP rloew, we will all miss you. Thank you for all you've done for the diehard Win9x community.

Apparently for all versions of Windows. Patched DOS can go to 32KiB Sectors for a maximum of 128TiB per Partition. Patched 9x can support Drives larger than 16TiB but with a maximum Partition size of 16TiB.

So it seems, for all practical purposes, 4KiB sectors are the upper limit, right?

I decided to take the plunge. I tried 8K and 16K Sectors. Neither worked in XP. CHKDSK did seem to understand and repair a NTFS Partition. Formatting failed for either FAT32 or NTFS. WD Formatter could reset and reformat the Drive. Windows 2000 rebooted when I connected the Drive with 16K Sectors. Windows 8 doesn't support 16K Sectors. Windows 98SE did not support 16K Sectors even after further patching of VFAT. Raw access was available, as well as ASPI so I can set or reset the Drive as needed. My RFDISK and RFORMAT tools can handle 16K Sectors as they were designed to support up to 32K Sectors.

For anyone still struggling to bite the bullet by installing a replacement to MSE (so far I'm finding them all downright scary if not outright destructive and it is just reminding me why I switched to MSE in the first place) these MSE registry changes seem to do two things. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates] "ASSignatureDue"=dword:0000016d "AVSignatureDue"=dword:0000016d ...where 16d = 365 days They stop the 2001 Event ID errors for Microsoft Antimalware, plus - and this did surprise me - my MSE has turned from orange back to green. This is deceptively comforting as it is obviously purely cosmetic. Even so MSE is not entirely useless as it is still doing its job even as the signature files become increasingly out of date. I'm guessing this gives 365 days before MSE thinks the 1.293.2807.0 definitions are too old. I'm also guessing the value could be increased even further. Ben.

It seems that Microsoft Security Essentials for Windows XP support has been dropped. Latest XP-compatible definitions https://definitionupdates.microsoft.com/download/DefinitionUpdates/VersionedSignatures/AM/1.291.2489.0/x86/mpam-fe.exe Attention: Link will not live long, download ASAP if You need it.

Two advantages to the SP approach vs the update pack is that this can be applied to either an installed running system or to an install medium, whichever you prefer, and it definitely takes less time to install a SP compared to applying all of the updates one at a time, even if you used an automated method to do so. Cheers and Regards