none
Determine WinCE Monthly Updates Programmatically RRS feed

  • Question

  • Hi,

    We are using WinCE 7.0 in our design.

    Is there anyway to determine programmatically (some script or code) the monthly updates that have been applied to the machine in the following scenarios?

    a. On the build machine itself (e.g. reading some registry setting to determine that the latest update that was applied to the machine was July 2015)

    b. On the device running the build output (NK.bin) (e.g on the device running the NK.bin, some means to determine the same information if it is embedded in some way into the image itself? May be some API?)

    I am guessing (b) won't be possible and that might be OK for us, but I am assuming there must be some method to get this information on the build machine. I know manually it is possible to do so by running WinCE updater tool and it shows the current update level but we need to retrieve this information programmatically to automate our build configuration.

    Thanks,

    Samie

    Thursday, December 17, 2015 2:09 PM

Answers

  • Can't help with (b) but for (a) yes there is.  Years ago a very nice Microsoft engineer gave us an unsupported registry entry to read.   This method still works for us.  Notice that the installLevel listed (and used by the command line WEDU exe -installLevel= parameter) is one higher than you might guess, installLevel 0 and 1 both mean the initial install so update 1 = installLevel 2 = registry value 2.  For you, installLevel 50 means update 49 which means July 2015 QFE.

    For 32 bit machines:
     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A4FF3FC0-A8B3-47c2-8627-CE1D2988D0D8}]
    For 64 bit machines:
     [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{A4FF3FC0-A8B3-47c2-8627-CE1D2988D0D8}]

    Later a nice MVP at KrakLLC wrote up an article with more details:

    https://krakllc.wordpress.com/2011/12/01/how-to-check-the-current-install-level-of-compact-7/

    Good luck

    Sue Wolber

    Keysight Technologies (used to be Agilent Technologies, used to be Hewlett Packard...)

    • Proposed as answer by Keshava GN Monday, December 21, 2015 5:52 AM
    • Marked as answer by samie g Tuesday, January 12, 2016 9:21 AM
    Friday, December 18, 2015 5:52 PM

All replies

  • Can't help with (b) but for (a) yes there is.  Years ago a very nice Microsoft engineer gave us an unsupported registry entry to read.   This method still works for us.  Notice that the installLevel listed (and used by the command line WEDU exe -installLevel= parameter) is one higher than you might guess, installLevel 0 and 1 both mean the initial install so update 1 = installLevel 2 = registry value 2.  For you, installLevel 50 means update 49 which means July 2015 QFE.

    For 32 bit machines:
     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A4FF3FC0-A8B3-47c2-8627-CE1D2988D0D8}]
    For 64 bit machines:
     [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{A4FF3FC0-A8B3-47c2-8627-CE1D2988D0D8}]

    Later a nice MVP at KrakLLC wrote up an article with more details:

    https://krakllc.wordpress.com/2011/12/01/how-to-check-the-current-install-level-of-compact-7/

    Good luck

    Sue Wolber

    Keysight Technologies (used to be Agilent Technologies, used to be Hewlett Packard...)

    • Proposed as answer by Keshava GN Monday, December 21, 2015 5:52 AM
    • Marked as answer by samie g Tuesday, January 12, 2016 9:21 AM
    Friday, December 18, 2015 5:52 PM
  • Many thanks Sue.
    Tuesday, January 12, 2016 9:21 AM