Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


glnz

POSReady 2009 updates ported to Windows XP SP3 ENU

Recommended Posts

The six offered updates installed fine for me.
It took ages to scan again due to the presence of the Office updates.
Are these likely to be the last ones, or will there be some more next month I wonder?
I read somewhere (here probably!) that support for the Office 2007 Compatibility Pack ends next month, which would make sense as it's presumably 10 years after it was launched.

I've also installed the optional update KB4039111.
Anyone know what this actually is?
Its page on the MS site, which is linked to from many other sites, is just "page not found"!
:dubbio:

Share this post


Link to post
Share on other sites

11 hours ago, roytam1 said:

[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS]

[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES]

These 2 paths should be deleted from registry in order to get WU thinking this is really POSReady machine.

 

And what about this one?:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion] "FeaturePackVersion"="SP3"

Delete or keep?

 

Share this post


Link to post
Share on other sites
41 minutes ago, pcalvert said:

 

And what about this one?:


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion] "FeaturePackVersion"="SP3"

Delete or keep?

 

That one you must delete. The other two (WEPOS and WES, if set to 0000, may as well be left in place).

  • Upvote 1

Share this post


Link to post
Share on other sites

@Dave-H

KB4039111 (kernel32.dll, ntdll.dll, ole32.dll, rpcss.dll, sprv0407.dll, wordpad.exe, xpsp2res.dll)  is an update related to security updates KB4026061 (sprv0407.dll, wordpad.exe) and KB4018556-v2 (kernel32.dll, ntdll.dll, ole32.dll, oleaut32.dll, rpcss.dll, xpsp2res.dll).
Unfortunately, MS in KB4039111 has an older version (5.1.2600.7239) attached to the file "xpsp2res.dll" against KB4018556-v2 (5.1.2600.7248), which can not be updated in Windows XP "xpsp2res.dll". Hopefully, this bug will be fixed by a subsequent update.
This could cause problems with the English language version of Windows XP Professional (ENU), as well as with all language versions of Windows XP Home. In a test in the VMware with the English-language version of Windows XP Professional, I have not found any problems (The file "xpsp2res.dll" was installed with version 5.1.2600.7248)!

:)

 

 

Edited by heinoganda

Share this post


Link to post
Share on other sites
2 hours ago, Dave-H said:

The six offered updates installed fine for me.
It took ages to scan again due to the presence of the Office updates.

Thanks to @glnz, I knew which Office 2007 compatibility pack with SP3 updates to search (now @Bersaglio has kindly provided direct links to them), so I downloaded them and installed those four by hand. Afterwards my main machine took 47 minutes (main XP) or 35 minutes (secondary XP)  to find the other updates. Since there´s no need to reboot between them, the Office 2007 compatibility pack with SP3 updates are best downloaded and updated by hand... provided we know which KBs they are. We already know it's them that cause the long delays.

@Bersaglio: Why KB4039111is questionable/not recommended? :unsure:

Share this post


Link to post
Share on other sites
47 minutes ago, dencorso said:

Afterwards my main machine took 47 minutes (main XP) or 35 minutes (secondary XP)  to find the other updates.

Wow, tested for me on my virtual machine (1 core core 2 duo 2.4 GHz and 512 MB memory) after I installed the latest cumulative update of IE8 manuel, as well as updates for Office 2007 compatibility pack. With the following search and install I have completely 5 minutes needed! :blink:

:)

Share this post


Link to post
Share on other sites

Catching up to bersaglio's excellent set of links --

1)  Should I install KB4039111 on my XP Pro SP3?  It didn't self-install.  But why does bersgalio criticize it?  Does it smell bad or something?

2)  Since I have Office 2003 on my XP machine (with the 2007 compatibility pack), should I manually install KB4011134 and KB4011125?

3)  In my wife's mini-office running Win 7 Pro 64-bit, we are also using Office 2003 (with the 2007 compatibility pack).  Are there similar KBs for that combination of stuff?   (I am Mr. El Cheapo so we wouldn't spend more money on more recent Office, and it just works.)

Grazie - danke - merci.
_________________________

Edit - hold on hold on !!!!

According to https://support.microsoft.com/en-us/help/20170912/security-update-deployment-information-september-12-2017 and
https://support.microsoft.com/en-us/help/4011125/descriptionofthesecurityupdateforwordviewerseptember12-2017 and
https://support.microsoft.com/en-us/help/4011134/descriptionofthesecurityupdateforwordviewerseptember12-2017

KB4011134 and KB4011125 are for Word Viewer, not Word.

Should we run them for Office 2003 ????

Edited by glnz

Share this post


Link to post
Share on other sites
7 hours ago, dencorso said:

@Bersaglio: Why KB4039111 is questionable/not recommended? :unsure:

2 hours ago, glnz said:

1)  Should I install KB4039111 on my XP Pro SP3?  It didn't self-install.  But why does bersgalio criticize it?  Does it smell bad or something?

I've figured it out: problem is @heinoganda is so good at it that he replied to our questions before we actually posed them!!! See;

7 hours ago, heinoganda said:

Unfortunately, MS in KB4039111 has an older version (5.1.2600.7239) attached to the file "xpsp2res.dll" against KB4018556-v2 (5.1.2600.7248), which can not be updated in Windows XP "xpsp2res.dll". Hopefully, this bug will be fixed by a subsequent update.
This could cause problems with the English language version of Windows XP Professional (ENU), as well as with all language versions of Windows XP Home. In a test in the VMware with the English-language version of Windows XP Professional, I have not found any problems (The file "xpsp2res.dll" was installed with version 5.1.2600.7248)!

In fact, I have already installed KB4039111 and did not find any problem either, so I think it can be used safely all right. :yes:

 

Share this post


Link to post
Share on other sites
6 hours ago, glnz said:

KB4011134 and KB4011125 are for Word Viewer, not Word.

Should we run them for Office 2003 ????

Yes!:yes: These are critical updates for shared components (graphical component - gdiplus and usp10) used in both Word Viewer and full Office 2003.:)

Share this post


Link to post
Share on other sites
6 hours ago, dencorso said:

I've figured it out: problem is @heinoganda is so good at it that he replied to our questions before we actually posed them!!! See;

When I wrote this comment, which originally answered the questions of Dave-H and pcalvert, Dencorso wrote a comment to pcalvert at the same time, which I edited my comment to the extent that the part was removed at pcalver. Since I create my own Updaterollups where it is necessary to extract the individual updates from MS is the circumstance noticed because of the file xpsp2res.dll. At this point, however, I was just testing the various Updaterollups, where Dencorso has already published another comment. After the test, I have my comment because of the knowledge gained added. For this reason, there is a temporal discrepancy.

One might think, that MS to have evil intentions for the update KB4025398 from 08/28/2017 and KB4039111. Just suspect, that in a short time these errors happen! 

:)

Edited by heinoganda

Share this post


Link to post
Share on other sites

Bersaglio - thanks again for detail on KB4011134 and KB4011125.  I shall try them in my XP machine shortly.

Now, back to a related question - in my disguise as El Cheapo, we are running Office 2003 on my wife's important Win 7 Pro 64-bit machine.  To make matters more confusing, she then separately installed a newer version of Excel on top of it (probably 2013 - 32-bit).  So the machine has Excel 2013 and Office 2003 with the 2007 Compatibility Pack.

Are there any versions of KB4011134 and KB4011125 we should install on that Win 7 Pro 64-bit machine?

What happens if we don't?

Yes, I know this is .00001% off topic, but I am also El Shameless.

Thanks.

Share this post


Link to post
Share on other sites
1 hour ago, glnz said:

Are there any versions of KB4011134 and KB4011125 we should install on that Win 7 Pro 64-bit machine?

Yes, these updates can be (and should be because they fix critical vulnerabilities) installed on any system with Office 2003 regardless of x64 or x86 type of operating system.

P.S. By the way Office 2003 is a native 32-bit application so all updates for Office 2003 are 32-bit only. But it is perfectly fine to install it on 64-bit OS because all 32-bit applications should work on it without problems. Only native 16-bit applications will not work on 64-bit OS, You need to use 32-bit OS to run them.

Edited by Bersaglio
Add

Share this post


Link to post
Share on other sites

Just a quick clarification.
My xpsp2res.dll file is version 5.1.2600.7248 (despite having installed KB4039111).
My USP10.dll is version 1.420.2600.7334, and GDIPLUS.dll is version 5.2.6002.24180.
I'm using Office XP(2002) with the 2007 Compatibility Pack.
Does that sound right, or do I need any more updating?
:dubbio:

Edited by Dave-H
Typos

Share this post


Link to post
Share on other sites
1 hour ago, Dave-H said:

My xpsp2res.dll file is version 5.1.2600.7248 (despite having installed KB4039111).
My USP10.dll is version 1.420.2600.7334, and GDIPLUS.dll is version 5.2.6002.24180.

This is correct. There are exact same versions on my system. But Office 2003 (which is installed on my system) uses different dlls with same names:

gdiplus.dll (in \Program Files\Microsoft Office\OFFICE11\ folder) file is version 11.0.8443.0

usp10.dll (in \Program Files\Common Files\Microsoft Shared\OFFICE11\ folder) file is version 1.626.6002.24173

P.S. By the way, Office XP should use files with same names in similar folders (OFFICE11->OFFICE10) but support of Office XP has ended in July 2011 and I believe that there were no more updates for Office XP after that date.

Edited by Bersaglio
Add

Share this post


Link to post
Share on other sites

@Dave-H

If there was a problem with KB4039384, there would have been a corresponding comment from my side. Regarding KB4039111, a fader flavor remains due to the enclosed file xpsp2res.dll version 5.1.2600.7239, whether a more current version like the version 5.1.2600.7248 should have appeared here. This will ultimately show the upcoming updates.

:)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...