Centennial App Thread

    By lucaslurponedl,




    Windows 10 Centennial Packages (Created Post-Anniversary Update)


    Note: These will only work on Windows 10 build 14393+ (aka the Anniversary Update RTM General Availability build) 


    Update : supports build 14901 (rs_prerelease) aka Redstone 2

    Update 2 :  all centennial packages support 15xxx Redstone 2 builds both created post anniversary and pre anniversary update)



    Steps to install are different as these are not packaged signed AppX packages.


    Note: These apps are up-to-date (as of 10th August 2016 00:00 BST)


    1. Enable Developer Mode (always required unless installing from the Store)

        To do this -- Open Settings >> Update and Security >> For developers >> Select Developer Mode


    2. Download any one of the packages below and follow the instructions below to install, making sure you have already enabled Developer Mode.


    3. Extract the zip file and you should have a folder called [Program-Name]PackageFiles.


    4. In an elevated PowerShell run this command:


    Add-AppxPackage "<Download Location>/[Program-Name]PackageFiles/AppXManifest.xml" -Register


    For example: ----  Add-AppxPackage "C:/Users/Bob/Downloads/VLCPackageFiles/AppXManifest.xml" -Register


    5. Enjoy your new app.










    warning: do not delete the PackageFiles otherwise the apps will not work. I also suggest you put these apps somewhere where you wont move them, because moving the Package files will also result in the apps not working.


    If anybody wishes to package these as AppX - then sign the apps under CN=CentennialApps.





    Windows 10 Centennial AppX Packages (Created Pre-Anniversary Update)


    Note: These will only work on Windows 10 build 14376+

    You must do both Step 1 and Step 2 in order to install the AppX packages.


    1. Enable Developer Mode

        To do this -- Open Settings >> Update and Security >> For developers >> Select Developer Mode


    2. Download certs.zip from here >> Extract both FrontMotion.cer and FrontMotion.pfx and follow instructions below.

        i. Double click on "FrontMotion.cer"
        ii. Select the "Store Location" as "Local Machine"
        iii. Click "Next" until you get to the "Certificate Store" page
        iv. Select the "Place all certificates in the following store" radio button
        v. Click "Browse"
        vi. Select the "Trusted People" certificate store
        vii. Click "OK" and "Next"
        viii.  Click "Finish"
        ix. Repeat Steps i-viii for "FrontMotion.pfx"


    3. Download any one of the AppX packages below and follow the instructions below to install, making sure you have already done the steps above.


    4. Double Click the AppX package and install.


    5. Enjoy the App!




















    You may post your appx files below if you wish to.

    [Unofficial] [Centennial] [10.0.14342.1000] Mozilla Firefox 46.0 v2

    By lucaslurponedl,

    Web-Browsers-Firefox-Metro-icon.png Mozilla Firefox (Centennial)


    Unofficially I am releasing the first fully ported Mozilla Firefox, featuring the file associations, the ability to set the default browser and with a modern icon.


    The functionality is exactly the same as in browsing experience as the other post I made with the same instructions (attached within updated zip)


    Link to MEGA


    Install Note: You must FIRST enable development mode in the settings app.

    Open settings > update and security > for developers > select development mode. (thanks @ReztaNZ)


    Development Branches for RTM

    By lucaslurponedl,

    Release to Manufacturing Builds (for reference)


    Windows XP




    Windows Vista




    Windows 7




    Windows 8




    Windows 8.1




    Windows 10 (Original Release)




    Windows 10 (November Update)




    Windows 10 (Anniversary Update)


    Note: This is the latest internal build 

    Note: This also follows the same development naming scheme as the November Update






    RTM Branches since Windows XP


    xpclient, vista_rtm, win7_rtm, win8_rtm ,winblue_rtm,th1, th2_release, rs1_release


    xpclient - Windows XP (nothing wrong here)


    vista_rtm - Windows Vista (nothing wrong here)


    win7_rtm - Windows 7 (nothing wrong here)


    win8_rtm - Windows 8 (nothing wrong here)


    winblue_rtm Windows 8.1 (wut?)


    This is odd being the fact that blue is the codename for 8.1 and I would have expected the branch to be called something like:




    which would have made more sense. But sure why not Microsoft.


    Okay.... Moving on


    th1 - Windows 10 Official Release (new naming structure, okay I get you here Microsoft)


    th2_release - Windows 10 November Update (wut?)


    Knowing there is already a TH2 branch (10587?), what's the difference Microsoft? Changing the naming structure again, splitting the internal development and the release which would be the same?


    rs1_release - Windows 10 Anniversary Update (wut?)


    Knowing there is already a RS1 branch. I'm wondering now if Microsoft is keeping this naming structure.


    Moving on to something different... or is it?


    Redstone Wave 2 (MS-vnext.net)


    rsmain  If this is a real development branch . What the HELL? - Microsoft, you are one confusing group of people when it comes to their branch naming structure.


    Hopefully Microsoft it turns out to be that rsmain is equivalent to a RS2 branch and we get rs2_release as the RTM. Otherwise its messed up. Keep a good naming structure. If you do decide to keep this well... STICK WITH IT.

Portal by DevFuse · Based on IP.Board Portal by IPS