none
Rebranded from POSReady 2009 to Windows XP Embedded after updates RRS feed

  • Question

  • We are currently building a Windows Embedded POSReady 2009 image for a number of touch based terminals.

    I started off by installing the base OS POSReady 2009 (non-evaluation version) and ran the windows update. After about 142 updates later my OS is now rebranded to Windows XP Embedded(System Properties, Login screens, etc...). I was able to narrow down the problematic update to 

    KB975713
    http://technet.microsoft.com/en-us/security/bulletin/MS10-007

    due to the severity of the update and our terminals having a network connection we can not exclude the update from the build. I also checked the underlying OS using the method advised here 

    http://social.technet.microsoft.com/Forums/en-US/cd3a07e5-87c0-429e-ac81-4223dbb5e91b/xpe-vs-wepos?forum=posready

    both pre and post updates are the same (HKEY_LOCAL_MACHINE\SYSTEM\WPA\POSReady = 1). Would it be safe to assume the rebranding was skin deep?

    This caused issue with our users as they are questioning our choice of OS due to Windows XP Embedded having a shorter end of life support vs Embedded POSReady 2009.

    http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=embedded&Filter=FilterNO

    We have thought about changing the images inside the dlls but decided it will violate the EULA. Is this correct?

    The question is how would we go about changing the brand of the OS back to POSReady 2009 without violating the EULA?



    • Edited by PeterPhan Monday, March 31, 2014 11:36 PM typo
    Monday, March 31, 2014 11:31 PM

Answers

  • Hi Roman,

    We have found the causing issue.

    The issue was us installing the Windows XP Service Pack 3 on top of the existing POSReady 2009 OS prior to running windows update. Once we excluded the SP3 from the install, all updates installed correctly without issues.


    • Marked as answer by PeterPhan Wednesday, April 2, 2014 2:19 AM
    Wednesday, April 2, 2014 2:18 AM

All replies

  • We also include KB975713 from February 2010 in our master image but did not see any rebranded screens like you described. Can you reproduce the issue? What are the exact steps for being able to reproduce your problem?

    Changing the DLL's resources, e.g. with 'Resource Hacker', is not allowed.


    Best regards, Roman Maier

    Tuesday, April 1, 2014 11:12 AM
  • Hi Roman,

    We have found the causing issue.

    The issue was us installing the Windows XP Service Pack 3 on top of the existing POSReady 2009 OS prior to running windows update. Once we excluded the SP3 from the install, all updates installed correctly without issues.


    • Marked as answer by PeterPhan Wednesday, April 2, 2014 2:19 AM
    Wednesday, April 2, 2014 2:18 AM
  • POSREady 2009 should have Xpe SP3 already built in.

    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET


    Wednesday, April 2, 2014 12:13 PM
    Moderator
  • That's right, POSReady2009 is built from Windows Embedded Standard 2009-sources which includes Service Pack 3.

    Unfortunately there are some (minor) differences to Windows XP Professional SP3 that have to be considered.


    Best regards, Roman Maier

    Wednesday, April 2, 2014 12:17 PM
  • Minor differences?

    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    Thursday, April 3, 2014 11:48 AM
    Moderator
  • Yes, for example that there is already IE7 included out-of-the-box instead of IE6, etc. (newer software versions), that there is 'fbreseal -keepall' optionally available instead of SysPrep and unattended setup is completely different. Additionally POSReady2009 comes with some interesting EEFs: FBWF for instance.


    Best regards, Roman Maier

    Thursday, April 3, 2014 11:53 AM