daniel_k
Content Type
Profiles
Forums
Events
Posts posted by daniel_k
-
-
16 minutes ago, IntMD said:
Even with the 2016 build from MDL? It still works for me with the wsusscan2.cab with dual-signed SHA1 & SHA256.
Yes, gave up and tried the MS script.
1 minute ago, Dave-H said:Just to add, I did stop the Automatic Updates service, disabled the DataStore folder by renaming it (I don't want to lose my update history) and when I ran the script it started the service again and recreated the folder, which is expected I assume.
Still the same end result though.
What about restarting Windows after renaming the folder, leaving the service disabled?
I'm running an untouched ENU XP SP3.0 -
Thanks for finding out the offending updates.
Just got a list of official XP SP3 updates, will download and unpack them all.
Then see what was the last official update including the files in KB4019276 and KB4459091.0 -
Couldn't get WUMT working.
However, the script on this article worked on a clean install of XP SP3:
https://docs.microsoft.com/en-us/windows/win32/wua_sdk/using-wua-to-scan-for-updates-offline
Save the text as a .vbs file (ie: wuscan.vbs), copy wsusscn2.cab to c:\ or change its path in the script, then run in a Command Prompt:cscript wuscan.vbs
If it doesn't work, try to:
- restart Windows
- stop Automatic Updates service, delete C:\WINDOWS\SoftwareDistribution\DataStore and re-enable the service.If it says Searching for updates... then just wait, it's doing its job.
1 -
1 hour ago, Dave-H said:
I think this is an operating system problem, the encryption types are not something that comes with Office itself, they are part of the OS.
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.
1 -
Let me clarify a few things. as I've spent several days creating this:
- .msu files can't be used to install many updates at a time: those packages include an update scanner (wsusscan.cab) to check applicability, which is run before installing every update and gets slow and slow over time. Svchost also consumes more and more RAM until your system crashes.
- .cab files are installed immediately, the check for applicability occurs during install, thus is faster and reliable.
- some updates have pre-requisites that require a restart. Because of this, I've split the updates in 3 parts.
2 -
3 hours ago, Dylan Cruz said:
I've sort of done the same thing, but only for 32-bit.
Maybe we can compare? It'd be good to know I didn't miss anything.
I just updated my list from February to July this morning. Not a list so much as all the actual updates themselves, ready to slipstream.
Hi, here is my list of updates (applies to both 32-bit and 64-bit).
Office / Project / Visio / SharePoint Designer 2010 Post-SP2:
Definition Update for Microsoft Office 2010 (KB3115475)
Security Update for Microsoft Access 2010 (KB4464527)
Security Update for Microsoft Excel 2010 (KB4484415)
Security Update for Microsoft InfoPath 2010 (KB3114414)
Security Update for Microsoft Office 2010 (KB2553313)
Security Update for Microsoft Office 2010 (KB2553332)
Security Update for Microsoft Office 2010 (KB2589288)
Security Update for Microsoft Office 2010 (KB2850016)
Security Update for Microsoft Office 2010 (KB2880971)
Security Update for Microsoft Office 2010 (KB2881029)
Security Update for Microsoft Office 2010 (KB2956063)
Security Update for Microsoft Office 2010 (KB2956076)
Security Update for Microsoft Office 2010 (KB3114565)
Security Update for Microsoft Office 2010 (KB3191908)
Security Update for Microsoft Office 2010 (KB3203468)
Security Update for Microsoft Office 2010 (KB3213626)
Security Update for Microsoft Office 2010 (KB3213631)
Security Update for Microsoft Office 2010 (KB3213638) - XP ONLY
Security Update for Microsoft Office 2010 (KB4011610)
Security Update for Microsoft Office 2010 (KB4022206)
Security Update for Microsoft Office 2010 (KB4022208)
Security Update for Microsoft Office 2010 (KB4484238)
Security Update for Microsoft Office 2010 (KB4484266)
Security Update for Microsoft OneNote 2010 (KB3114885)
Security Update for Microsoft Outlook 2010 (KB4484382)
Security Update for Microsoft Project 2010 (KB4484463)
Security Update for Microsoft Publisher 2010 (KB4032216)
Security Update for Microsoft Visio 2010 (KB4462225)
Security Update for Microsoft Visio Viewer 2010 (KB2999465)
Security Update for Microsoft Word 2010 (KB4461625)
Security Update for Microsoft Word 2010 (KB4484458)
Update for Microsoft Excel 2010 (KB2956084)
Update for Microsoft Filter Pack 2.0 (KB3114879)
Update for Microsoft InfoPath 2010 (KB2817369)
Update for Microsoft Office 2010 (KB2553140)
Update for Microsoft Office 2010 (KB2553347)
Update for Microsoft Office 2010 (KB2553388)
Update for Microsoft Office 2010 (KB2589298)
Update for Microsoft Office 2010 (KB2589318)
Update for Microsoft Office 2010 (KB2589339)
Update for Microsoft Office 2010 (KB2589375)
Update for Microsoft Office 2010 (KB2589386)
Update for Microsoft Office 2010 (KB2597087)
Update for Microsoft Office 2010 (KB2791057)
Update for Microsoft Office 2010 (KB2825640)
Update for Microsoft Office 2010 (KB2881030)
Update for Microsoft Office 2010 (KB2883019)
Update for Microsoft Office 2010 (KB3054873)
Update for Microsoft Office 2010 (KB3054886)
Update for Microsoft Office 2010 (KB3055047)
Update for Microsoft Office 2010 (KB4092436)
Update for Microsoft Office 2010 (KB4461579)
Update for Microsoft Office 2010 (KB4461626)
Update for Microsoft Office 2010 (KB4462172)
Update for Microsoft Office 2010 (KB4462187)
Update for Microsoft Office 2010 (KB4484377)
Update for Microsoft Office 2010 (KB4484454)
Update for Microsoft Outlook 2010 (KB3114559)
Update for Microsoft Outlook Social Connector 2010 (KB2553308)
Update for Microsoft PowerPoint 2010 (KB4092435)
Update for Microsoft Project 2010 (KB3054882)
Update for Microsoft SharePoint Designer 2010 (KB2881023)
Update for Microsoft SharePoint Workspace 2010 (KB2760601)
Update for Microsoft Visio 2010 (KB2881025)
Update for Microsoft Visual Studio 2010 Tools for Office Runtime (KB3001652) - Must be run manually (.exe)Security Update for Microsoft Office 2010 (KB4092483) - XP-compatible MSO.DLL according to @Dave-H
Business Contact Manager Post-SP1:
Service Pack for Business Contact Manager for Microsoft Outlook 2010 (KB2553006)
Security Update for Microsoft Chart Controls for Microsoft .NET Framework 3.5 Service Pack 1 (KB2500170)
SQL Server 2008 Express SP21 -
I've just finished an update list of Office 2010 (32/64-bit). The patches are automatically applied during installation.
Anyone interested? If so, should I create a topic in the Office section?2 -
2 minutes ago, IntMD said:
slightly stupid idea - if it would actually depend on the files from the windows update agent, then maybe hexedit them to replace each instance of old url to the new one. similar to the trick used to get msn clients connected to custom servers. not sure if this would just be enough, but still.
Actually, it has nothing to with the WU Agent. Except for the WU site url, there is no hardcoded address.
The WU site provides the Agent with the "service" url.
Maybe we could setup a local proxy with url forwarding?
I'm not used to these things.0 -
Just checked the WindowsUpdate.log on Vista, XP and Win7, the block is in the remote WU servers.
On supported OSes, this url is used to check for updates:
https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
On unsupported OSes, this url is used to check for updates:
http://www.update.microsoft.com/v6/ClientWebService/client.asmx
But it was deleted.
If we could redirect it to the link above, maybe it would still work.
Any ideas?2 -
Was working a few hours ago.
Now they killed it for sure:WARNING: SyncUpdates failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
Database was deleted. RIP.
2 -
It seems that Microsoft just removed www.update.microsoft.com
http://fe2.update.microsoft.com tries to load the service, but redirects to www.update.microsoft.com and fails.
Tried to redirect the www address to the fe2 IP, but didn't work when using hosts file?
Anyone has another idea?0 -
I wouldn't be surprised if Microsoft would completely wipe the Catalog, leaving only updates for Windows 8.1 and later.
Those who have any interest on old OSes should download everything ASAP.
Microsoft seems to taking seriously this time.0 -
Did Microsoft already pull the plug on Microsoft Update (which includes Office updates)?
Installed Office 2010 just to grab a list of updates, but it just keeps scanning for updates forever.0 -
Hi, I'm busy with other stuff, so can't provide you with a script/batch file to rename the files.
I'm sure you'll eventually figure it out by yourself.For obvious reasons, you shouldn't have such long filenames to avoid issues during installation because of long pathnames exceeeding MAX_PATH size.
2 -
I'll send you a PM with files/directions.
1 -
19 minutes ago, daniel_k said:
let me know the folder where AsusTPApi.dll is copied to.
0 -
On XP.
Even if it doesn't work on 8.1, I'd try it on XP anyway, as sometimes the manufacturer disables the driver/control panel when an unsupported OS is detected.
Regarding the fix for SmartGesture 1.0.27 (I've linked above), we need to patch AsusTPApi.dll and copy Vista beta build 5048 versions of powrprof.dll and setupapi.dll, which include the missing functions.
If you do manage to get the package installed on XP, let me know the folder where AsusTPApi.dll is copied to.
Is QuickGesture.exe loaded during boot on Windows 8.1? This one it's harder to fix, as it uses Windows 8 Gesture API.0 -
Did you try to install the Elan "10.5.9.0" driver from jaclaz?
I've got na idea. Download this:
http://ftp.tekwind.co.jp/pub/asustw/nb/Drivers/Touchpad/SmartGesture_Win7_64_Z1027.zip
If you run setup, does it proceed with the installation?
If so, I already have a fix for the missing API calls, you just need to replace some files.0 -
31 minutes ago, Dave-H said:
Thanks very much @daniel_k!
The second one looks like it's 64 bit only, so that wouldn't be any good, I need a 32 bit driver.
I will check out the first one though, it's not clear what architecture that is.
Did you run the installer?
I've extracted the files by "running" the MSI in Administrative mode:
msiexec /a SetupTPDriver.msi
I've packed the drivers for you (the settings you need to "copy" from Windows 7/8.1, as the apps are heavily Vista+ dependant):
https://www.mediafire.com/file/d9hfe8xjw1648370 -
Hi, found these which definitively work on XP.
http://dlcdnet.asus.com/pub/ASUS/nb/DriversForWin8/SmartGesture/SmartGesture_Win7_8_VER201.zip
01/10/2013, 1.0.0.170http://dlcdnet.asus.com/pub/ASUS/nb/Apps_for_Win10/SmartGesture/SmartGesture_Win10_64_VER4023.zip.zip
01/13/2015, 1.0.0.2330 -
Here is the latest/last driver for XP, which fixes the KRACK vulnerability.
1030.31.0102.2018 (Nov 6, 2018)0 -
@jaclaz
Pretty sure this is a driver feature.
Basically it does what certain USB to SATA bridge controllers do.
It detects the disk geometry and automatically changes the sector size reported to Windows according to the table I've posted earlier.
At the same time, it "combines" as many 512 bytes sectors as need to match the sector size reported.
The driver has some kind of protection.
I've almost got it to work: currently only detects optical drives.0 -
5 hours ago, jaclaz said:
Maybe - just maybe - having a number of "near enough" versions someone with the right knowledge of capability (as an example daniel_k
) may be able to understand what exactly makes these drivers so special, though we don't know if the "variable sector size" is something that is in the driver only or if it is a specific feature of the actual controller chip and the software only "switches modes".
A (hopefully "pristine" and unmodified) version 3.1.1540.86 can be found on Acer's site, as a driver for the model Aspire 4535G:
Hopefully @Snear is able to test the drivers I've posted here (specially the v3.1 ones).
Thanks for the Acer link, it's exactly the same driver I've packaged.
I'm sure this AHCI/RAID driver written by Promise automatically changes the sector size according to the disk size.
Found an article on Promise's KB regarding support for disks larger than 2TB:For this logical drive size | Select this sector size Up to 16 TB | 4096 bytes (4 KB) Up to 8 TB | 2048 bytes (2 KB) Up to 4 TB | 1024 bytes (1 KB) Up to 2 TB | 512 bytes (512 B)Understanding the 2 TB Limit in Windows Storage TechNet article has comments from owners of Promise products that confirm 7.5 TB disk being usable with Windows 2000 Server.
1 -
19 hours ago, jaclaz said:
@daniel_k
What does NAPA series mean?
As a personal favour (only if you wish, of course
):
Please, please, please, do not use the .rar format as it is NOT a "universal" format, a lot of other tools (but WinRar) have issues with it.
NAPA is the codename of the SATA controllers using Promise's IP.
Sure I can use 7-Zip. Replaced .rar with .7z package.
I'm use WinRAR because of the Recovery Record feature for safety reasons.0
) to identify which one breaks Office.
):
Beware of Office 2010 Updates!
in Pinned Topics regarding Windows XP
Posted
@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.