If you are seeing this error, never fear. Your computer files haven’t fallen through a black hole, or travelled back in time… and OneDrive Sync is probably working just fine.
Time in relationship to Computers, Devices, Operating Systems, etc all began on January 1st 1970. January 1st 1970 is considered the Epoch Time, and all minutes, hours days, weeks, months, and years since January 1st 1970 are counted in the number of seconds since 1970.
Today’s date 9/9/2014 at 11:27AM EST represented in EPOCH time is 1410276437 or 1410276437 since January 1st 1970.
The reason your Computer, Device, OS, is blinking 12/31/1969 (prior to EPOCH time ) is that it is having an issue with either its internal clock, or the clock for the service it is trying to contact.
In this particular case, OneDrive is having an issue translating the Computer clock time into EPOCH time….so it displays the time in the only thing it understands which is 12/31/1969.
It’s kind of like you thinking the date is 12/31/1969 when you don’t know what date it is. You don’t behave that way, because you are a person and not a dumb machine. You can remember yesterday. You don’t care what the date is…. You just know you’re late for work again.
Computers can’t do that. They have to know how many seconds have elapsed since 1/1/1970 in order to know what date/time it is.
I gotta go. I’m a day late for a class.
Dave
Recently I was pulled into a customer engagement, where the customer had recently deployed Office 365 for their users. While they loved the benefits of O365, they couldn’t quite get their head around allowing O365 to update on its own when a user launched Office, and a new update was available.
Their goal then, was to disable the Automatic Update feature of O365 and replace it with a scheduled and targeted Update from System Center Configuration Manager. Once this was done, they could control what version of O365 was deployed across all of their systems, how and when their client machines were updated, and if necessary, rollback to previous versions of O365.
Follow along, shall we?
To do this, the first step is to disable the Automatic Update feature of O365. Load the Office 2013 Administrative Template files into Group Policy. You can find them Here: Office 2013 ADMX ADML Files and Office Customization Tool.
Following this TechNet article to use the new Group Policy Settings to customize Office 2013 Use Group Policy to enforce Office 2010 settings.
Pay particular attention to this GPO setting:
Microsoft Office 2013 (Machine)\Updates
Enable Automatic Updates
This policy setting controls whether the Office automatic updates are enabled or disabled for all Office products installed via Click-to-Run. This policy has no effect on Office products installed via Windows Installer. If you enable or do not configure this policy setting, Office periodically checks for updates. When updates are detected, Office downloads and applies them in the background. If you disable this policy setting, Office won't check for updates.
HKLM\software\policies\microsoft\office\15.0\common\officeupdate!enableautomaticupdates
Once you have disabled O365’s ability to update itself, you’ll need to setup Configuration Manager 2012 to kick off the Office Update feature known as Click2Run.
Here’s how to do that.
Create a Collection that will contain the target machines you want to update with Click2Run. In my lab I only have one client (Windows 8.1) that I’m going to use for this demo). It is in a Collection of it’s own.
Next create an empty package. “But Dave, why an empty package?” you say. Just follow me on this one….all shall become clear in due time.
Create a Package without any Source files.
I called my package OfficeC2RClient. I gave the Package the same version as the version of O365 I was updating.
You can find a list of all the Office 365 Versions and their Version information
HERE: Microsoft Office 2013 Click-to-Run Virtualization
In my lab, the Package name is OfficeC2RClient (and for fun, I’m listing the Version of O365 that I want to update to with this package. The full version number is 15.0.4631.1004 (which we will use in a minute).
Notice on the Data Source tab, I don’t point to any source files. There is a really great reason for this. In this example we’re going to use the built in functionality of O365 to patch itself, but calling it as a command instead of distributing it as a package.
“Hey Dave!” You might say, “We could go grab the Office Click to Run executable and push it with Configuration Manager 2012. Couldn’t we?”
Yes we could make that the Source Files for our Package, distribute it across our Configuration Manager 2012 Distribution Points and push it like any other package to our client O365 machines to kick off their update.
But we don’t really want to. The reason for this, is that this file gets updated by 0365 itself. Every time the file is updated, we’d have to pull it from a client source, repackage it, and redistribute to our Distribution Points….and that’s a lot of time wasted.
What we’re going to do instead is add a Program to our package that simply calls the officec2rclient.exe that already exists on each client machine.
The syntax for the Program will be "Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe" /update user updatetoversion=15.0.4631.1004
This is what our Program looks like.
And we’re making sure that we let it run “Whether or Not a User is Logged On.”
Now we create a Deployment for our Package/Program.
The Deployment allows us to Target our Collection that contains the Office 365 clients we want to patch.
Now add the Distribution Points (just for fun).
Nothing to see here. Keep moving….
In my lab, I want OfficeC2RClient.exe to check for Office 365 updates once a month on the Last Friday of the Month.
The schedule looks like this:
Click on thru the Deployment Wizard and then Done!
Now on the Last Friday of every 1 months…
My Windows 8.1 client is getting its Office 365 update as Targeted and Scheduled by Configuration Manager 2012, but using the building officec2rclient.exe. (Could we hide the above splash screen? Of course! Using the /displaylevel variable |False you can prevent the User from seeing the splash screen interface during the update. More details on that Here: Click-to-Run for Office 365 and its associated command-line switches
After the updates are downloaded, they get applied.
And finally checking to ensure the Version that we pushed is the Version that we got….
We pushed "Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe" /update user updatetoversion=15.0.4631.1004
And we got….
And that’s all folks! Questions? Comments?
SPECIAL THANKS TO: Alan Ross, Brian Moreland, Matt DePietro and Daniel Earnest for their background on Office 365 and support with this customer’s question!
“MAKE IT STOP!” was the subject of the e-mail I received yesterday from a customer who was incredibly frustrated with an issue on his new Windows 8.1 laptop.
Have you ever seen this? You click on an app you got from the Windows 8.1 Store and it won’t open? You click on the app, but the app simply reloads the Start screen.
(Actual closing behavior not pictured because reasons!)
This is apparently a not uncommon issue if the permissions for the "All Application Packages” group have changed in the registry or to specific folders. These changes to the registry can be caused either by User action or by a Group Policy that has been applied to a domain joined machine.
How to fix this:
(1) Open the Registry (REGEDIT)
Check that the All Applications Packages group has READ permissions to each of the following registry paths.
This shows that HKEY_CLASSES_ROOT has READ Permissions for the All APPLICATION PACKAGES group. You’ll need to check this for each of the registry paths listed above.
(2) Open File Explorer
Open your OS Drive (C).
Then select the Program Files folder and select Properties.
In Program Files Properties select the Security Tab.
On the Security tab click on Advanced.
On the Advanced Security Settings for Program Files screen verify that ALL APPLICATION PACKAGES has Allow Permissions Read & execute for This folder, subfolders and files.
(3) If you are unable to make the changes to the Registry or the folder permissions to Program Files, it is likely that your issue is caused by a Group Policy applied by your Domain Administrator that prevents Windows Store Apps from launching.
You can verify that this is the case by running the following:
Open an Administrator Command Prompt from your Start button.
Type the following in the Administrator Command Prompt
“gpresult /h c:\gpresults.html” without quotes.
Wait until the Report is finished being generated.
Open the report location c:\gpresults.html
Your report will look something like the below screen capture.
Look for Computer Settings – Policies\Windows Settings\Security Settings. Check for both “File System” the entry for Registry. If you have settings here then you need to talk to your Domain Administrator about what Group Policy Objects are being applied, and how you can get the All Application Packages group the proper permissions via the Group Policy Object.
Direct your Domain Administrator to MSKB Article KB2798317 to resolve this issue.
I’ll be updating this article over the next couple of days with additional troubleshooting steps.
8/4/2014 10am – Windows Phone 8.1 Update Cyan on my daughter’s non-Developer Preview Lumia 520.
------------------------------------------------------------------------------
8/4/2014 8AM - Update #4 – Nokia has yet to update their Update Release page HERE , but as of 8am EST the Windows Phone 8.1 Update (Cyan) is available and OTA on ATT.
This is currently installing on my 1020, my daughter’s 520, and my wife’s 920.
Most notable about this update, is how quickly it installs OTA.
-----------------------------------------------------------------------------------
7/21/2014
Nokia has updated their phone release pages with a new article titled All-new Windows Phone experience: Lumia Cyan update. On this page you can read about all the new features in Windows Phone 8.1 such as Word Flow, Cortana and the Windows Phone 8.1 Action Center.
Update Availability has changed for the Lumia 1520 on ATT in USA to AVAILABLE.
ATT has updated their Software Update Page to include the update for the Nokia Lumia 1520. Read about that here Update the Software for the Nokia Lumia 1520
If you already have a Windows Phone 8, and want to know when the 8.1 update will be available, check out the official Nokia page: HERE.
Last week headlines exploded on every device I own “Computer passes the Turing Test”. If by some chance you missed this so-called Technological Milestone, you can read about it here Computer passes Turing Test.
I, for one, am entirely skeptical. Alan Turing (for whom the Turing test is named) posited in 1950 that determining if a computer could ‘Think’ was not possible, but that determining if a computer could IMITATE thinking was possible.
The recent test at the University of Reading which pitted a computer imitating a 13 year old boy against a 30 judges to see if they could determine if the Persona Eugene Goostman was a computer or a real 13 year old boy, does not give the result the testers want you to accept.
10 of the 30 judges ruled that the AI (artificial intelligence/persona) was a real boy. Pinocchio would be proud.
However, is this really passing the Turing test? I say, no. It is not.
Objection #1 – Only 1/3 of the judges believed they were talking to a real boy.
To begin with the 30 judges were specifically told they were talking to a 13 year old boy from the Ukraine. This was to establish any awkward wording or delayed response as natural human translation/comprehension/syntax issues.
We’ll call that Objection #2 – The Judges were pre-disposed to believe they were talking to a human.
Additionally the Turing test supposes that a computer can imitate a human personality for a brief conversation, limited to text chat only. But as devices and computers become more and more connected to the internet (the so-called Internet of Things, the integration of Search (Bing.com and Google) into devices and AI (personas) is inevitable. Take for example Cortana. Bing already has a persona in Cortana which currently runs on Windows Phones. More about Cortana here Meet Cortana
These devices would then be able (with a persona attached) to be instantaneous experts connected to Search engines and access subject matter that the ordinary person would have no real use for.
Wouldn’t it be possible then, to easily ask via a text chat, a question to a supposed 13 year old boy, that a 13 year old boy should not be able to answer?
For example if I asked via chat what I assumed was a 13 year old boy “Who painted “The Second of May 1808 (The Charge of the Mamelukes)?”” and the ‘child’ immediately responded that Francisco Goya painted it in 1814 in the two month period he also painted “The Third of May”, I might be a little suspect that I wasn’t text chatting with a real child.
The Second of May 1808
There are numerous examples that could be given here for a persona that was supposedly of any age or sex. Questions could be posited that the very persona should not reasonably be able to answer.
We’ll call this Objection #3 – Computer AI has access to information at speeds well beyond human comprehension. In order to successfully mimic a human, the AI would have to play dumb. This invalidates the Turing Test.
This also makes the Turing test incredibly difficult to pass, or at the most, possibly not really a valid test of computer AI/mimicry.
A computer AI that can text chat, that can interact with humans naturally, and that can play games, instruct, converse naturally does not need to pass as human, and probably cannot. Any long term exposure to an AI will begin to show patterns and flaws in the personality or superior skill in the personality that is NOT Human.
Perhaps, we need to better define what is human, to understand what is not?
Objection #4 – We haven’t defined what human is.
For now…. to quote my friend Andy Garlington (quoting War Games)
“Shall we play a game?”
A customer recently complained to me “I wish I could get all the Security Updates on DVD instead of thru the WSUS catalog or Windows Update!”
I like requests like that one, because I get to have an easy answer, that immediately fills the customers request\need.
You can get all the Monthly Security Update Releases on a downloadable DVD from Microsoft.com
Microsoft now releases ISO-9660 DVD5 image files that contain all the security updates that are released on the Windows Update website. The ISO image files are released at the same time that security updates are released on the Windows Update website. The ISO image files are intended for corporate administrators who:
By using the ISO image files, administrators can download multiple updates in all languages at the same time.
Download your DVD ISO image file here KB913086
“Hey!” the e-mail began. “My Live Tiles aren’t Working! They are stuck! Help!”
‘Hey!’ I thought. ‘I know how to fix that!’
One of the coolest features of Windows 8.1 is Live Tiles. Live Tiles update frequently with the information you care most about, whether it is Weather, News, Sports, Technology, or just your friends latest Tweet or Facebook status; Live Tiles will get you that information and display it in an easy to consume way on your Start Menu.
Live Tiles in Windows 8.1
Fortunately issues with Live Tiles are rare and rather simple to troubleshoot. Some of this I have covered before (but not specifically in relationship to Live Tile issues) so please pardon duplicate info from previous blog posts.
1. Proxy Issues – if your internet connection is through a Proxy Server (usually a work laptop or desktop) and you have Windows 8 Live Tiles that aren’t updating you might want to try the steps listed here - Using authenticated proxy servers together with Windows 8
2. Try using WSRESET.EXE ( I wrote about this in a previous blog) Windows 8.1 and The Nuclear Option
2. Try using WSRESET.EXE ( I wrote about this in a previous blog)
Windows 8.1 and The Nuclear Option
wsreset.exe is a tool found in C:\%Windir%\System32\ that “resets the Windows Store without changing account settings or deleting installed apps”
Simply run wsreset.exe as an administrator and the Windows Store cache is cleared, and you can try loading the store or purchasing an app again.
The quick way to open the Administrator Command Prompt in Windows 8.1? Right click the Start Button and select Command Prompt (Admin).
After you run WSRESET.EXE in Windows 8 or Windows RT you will receive a message stating the Cache as been Cleared. In Windows 8.1 the store will simply open. For more info The Windows Club has a very brief write up here How to Reset The Windows Store Cache 3. Try running the Windows 8/8.1 troubleshooting diagnostics. The apps troubleshooter can help resolve issues with apps not running correctly, or issues with the Windows 8/8.1 App Store. Apps troubleshooter
After you run WSRESET.EXE in Windows 8 or Windows RT you will receive a message stating the Cache as been Cleared. In Windows 8.1 the store will simply open.
For more info The Windows Club has a very brief write up here How to Reset The Windows Store Cache
3. Try running the Windows 8/8.1 troubleshooting diagnostics.
The apps troubleshooter can help resolve issues with apps not running correctly, or issues with the Windows 8/8.1 App Store.
Apps troubleshooter
4. Check the following Registry Key ( HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Packages) Ensure that SYSTEM has all the Rights selected as shown.
4. Check the following Registry Key
( HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Packages)
Ensure that SYSTEM has all the Rights selected as shown.
5. Try syncing your App licenses from the App Store.
Open the Windows Store. From the Charms menu select the Settings option. Tap or click App updates. Tap or click Sync licenses.
Open the Windows Store.
From the Charms menu select the Settings option.
Tap or click App updates.
Tap or click Sync licenses.
‘
More Tips on Troubleshooting Live Tiles coming soon!
Ciao!
In a previous blog post, I reviewed an issue some users were having launching the Windows 8.1 App Store.
You can find that article here – Windows App Store doesn't load after 8.1 Upgrade You can also find an article I wrote about how to remove 3rd party Apps from Windows 8/8.1 using PowerShell here - How to Remove Windows 8.1 Store Apps with PowerShell when they won't go quietly.
These articles worked for many users, however a small, but vocal percentage were not able to resolve their issue using these simple steps. I’d like to review for those users, what other options they have to resolve this issue.
In this post, I’m going to quickly review several other options you can take if you want to fix App Store issues with Windows 8/8.1. I won’t cover them all, but I will be heavily editing this post in the future with further troubleshooting steps.
Option #1 – WSRESET.EXE
wsreset.exe is a tool found in C:\%Windir%\System32\ that “resets the Windows Store without changing account settings or deleting installed apps” Simply run wsreset.exe as an administrator and the Windows Store cache is cleared, and you can try loading the store or purchasing an app again. The quick way to open the Administrator Command Prompt in Windows 8.1? Right click the Start Button and select Command Prompt (Admin). For more info The Windows Club has a very brief write up here How to Reset The Windows Store Cache
Option #2 – Try running the Windows 8/8.1 troubleshooting diagnostics.
Option #3 – Try syncing your App licenses from the App Store.
Option #4 – The Nuclear Option.
The Nuclear Option is to Reset the PC. This is not an option that I recommend until many other options are eliminated (including many not in this article). To Reset the PC, you have two basic options: (1) Refresh your PC without affecting your files. Or (2) Remove everything and reinstall Windows. To Refresh your PC without affecting your files: From the Charms select Settings, and then select Change PC settings. (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, click Settings, and then click Change PC settings.) Select Update and recovery, and then select Recovery. Under Refresh your PC without affecting your files. Click Get Started. Follow the instructions on the screen.
The Nuclear Option is to Reset the PC. This is not an option that I recommend until many other options are eliminated (including many not in this article).
To Reset the PC, you have two basic options: (1) Refresh your PC without affecting your files. Or (2) Remove everything and reinstall Windows.
To Refresh your PC without affecting your files:
From the Charms select Settings, and then select Change PC settings. (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, click Settings, and then click Change PC settings.)
Select Update and recovery, and then select Recovery.
Under Refresh your PC without affecting your files. Click Get Started.
Follow the instructions on the screen.
To Remove everything and reinstall Windows: From the Charms select Settings, and then select Change PC settings. Select Update and recovery, and then select Recovery. Under Remove everything and reinstall Windows, select Get started. (I feel it is important to note here – this removes EVERYTHING from your PC, leaving only a fresh clean Operating System) If you have other issues with Windows 8/8.1 you’d like me to cover, feel free to drop me a line, or comment below. Dave
To Remove everything and reinstall Windows:
From the Charms select Settings, and then select Change PC settings.
Under Remove everything and reinstall Windows, select Get started.
(I feel it is important to note here – this removes EVERYTHING from your PC, leaving only a fresh clean Operating System)
If you have other issues with Windows 8/8.1 you’d like me to cover, feel free to drop me a line, or comment below.
Here’s an issue that I’ve only experienced once myself, but that anecdotal evidence says may not be a completely uncommon occurrence for some users.
You install an app from the Windows Store that either doesn’t install correctly (most likely due to an issue from the developer) or you decide that isn’t really your cup of tea.
You open the Start menu and try to Uninstall the app normally, by right-clicking the app tile and then selecting Uninstall from the context menu below.
I’m using the really wonderful app Network Speed Test for this example ( I personally love this app, and have never had issue with uninstalling it, but again this is just for example).
Now in my experience the app that wouldn’t uninstall had no reaction to my clicking the Uninstall button. I didn’t get an error message, the app just didn’t uninstall.
The next step was to open up PowerShell and ‘get under the hood’ so to speak. Open up Windows PowerShell as an Administrator.
At the PowerShell command prompt type ‘get-appxpackage’ and hit enter.
The list of installed applications will scroll past. You’ll need to scroll back thru them to find the application you can’t remove.
Alternatively you can type ‘get-appxpackage –Name *some portion of the name*’ to find your app package.
In the above example I typed ‘get-appxpackage –Name *speed* to find the package for Microsoft.NetworkSpeedTest
From this same output we also get the PackageFullName which will use to remove the package.
Now type ‘remove-appxpackage’ with the full package name. In my example I typed ‘remove-appxpackage Microsoft.NetworkSpeedTest_1.0.0.23_x64__8wekyb3d8bbwe –confirm’
The –confirm switch gives you a nice prompt to let you verify what you are doing before you commit. Hitting ‘Y’ the default proceeds with the Uninstall.
And now the pesky app is uninstalled (though in my test case I’ll be re-installing that app immediately).
A friend of mine called me in a panic because his Samsung tablet wouldn't upgrade to Windows 8.1.
Every visit to the Windows Store he was offered the Upgrade, but each attempt to upgraded ended in the error below:
Sometimes this error will read "Something happened and the Windows 8.1 could’nt be installed. Please try again. Error code 0×80240031"
Fortunately, this was a relatively simple fix.
First open up the Command Prompt as an Administrator:
At the Command Prompt type the following commands one at a time:
'net stop wuauserv' hit enter
'net stop bits' hit enter
Now browse to the C:\Windows\Software Distribution folder and delete all the files and folders inside.
You may be told files are in use, if so, restart your device, and run the commands above again,
but this time make sure the Windows Store app isn't open.
Now back to the Command Prompt and type the following commands one at a time:
'net start wuauserv' hit enter
'net start bits' hit enter
Now open the Windows Store. It should look like this:
Try the Upgrade again... It should start downloading like the below:
Enjoy Windows 8.1!
UPDATE #2 - If you are still having issues after trying these steps, please check out my article Windows 8.1 and the Nuclear Option for additional steps.
http://blogs.technet.com/b/ouc1too/archive/2013/12/31/windows-8-1-and-the-nuclear-option.aspx
After upgrading Windows 8 to Windows 8.1 on one of my laptops, I noticed that even though I was connected to the internet (via hotel wireless), the Windows Store didn’t seem to think I had any internet connection at all.
Opening the Windows Store would result in this page.
No proxy information was necessary for the internet hotel connection, but I did have to accept the hotel EULA before the hotel network quarantine handed me a valid IP. My assumption here, is that my poor little Intel(R) Centrino(R) Advanced-N 6205 wireless card just got stressed out and confused in the process. I decided to disable and re-enable the little guy to see if that would clear things up.
To do this open PowerShell as an Administrator
First things first, I had to get the names of my wireless network adapter to make sure I was fixing the right problem.
To do this type ‘Get-NetAdapter –Name *’ in the PS window.
This returns a list of network adapter names.
In my case, my wireless network adapter is named ‘Wi-Fi’.
So then I verified what command I needed to use to Disable and Enable my ‘Wi-Fi’ network adapter with the Get-Help NetAdapter command.
Combining the Disable-NetAdapter cmdlet with my wireless card’s name gives me this command.
‘Disable-NetAdapter –Name ‘Wi-Fi’’
And I then re-enable the adapter the same way.
‘Enable-NetAdapter –Name ‘Wi-Fi’’
I verified my laptop was back on the internet by going to www.bing.com, and then tried opening the Windows Store again.
Success. My network card is no longer confused.
If you've just upgraded your Windows 8 (non RT) device to Windows 8.1 and suddenly upon reboot you're facing a quietly humming computer with a black screen of nothingness....don't panic. You've probably just got Master Boot Record issues. This can be a fairly easy fix, particularly if you've already created a Windows 8.1 Recovery disk. If not, you'll need to use your bootable install media for Windows 8.1 or find a working Windows 8.1 device and create a recovery disk.
We'll assume that you don't have your bootable install media, and you've found a working Windows 8.1 device. On the working device, open the Charms and select Search.
In the Search charm type 'Create a Recovery Drive'
You'll get a prompt to allow the Recovery Media Creator Wizard to run, make sure you allow it. Insert a writeable USB Key (**warning** all content on this key will be deleted).
In the Recovery Media Wizard you'll specify this usb key as your Recovery drive.
The Recovery Drive Creator will wipe the usb key, and create a bootable partition with the Recovery tools installed. Once the wizard is complete, remove the usb key, and boot your impaired Windows 8.1 via the new usb Recovery Drive.
You may need to hit ESC or F9 during the reboot to select your boot drive. Here I hit ESC and selected the USB key I created during the Recovery Drive Creator.
From the Recovery Disk Menu - select Troubleshoot.
From the Troubleshoot menu - select Advanced options.
From the Advanced options menu select - Command Prompt.
In the command prompt - type 'bootrec /fixmbr'
Hit enter. Quickly you should see a confirmation like above. Type exit and hit enter.
You have two options back at this screen...you can continue to Windows 8.1 or (I recommend) Turn off your PC and restart it.
If you haven't already, remove the usb key, and start your device.
You should be back up and booting into Windows 8.1.
If you're currently experiencing abandonment issues from the Windows Store after upgrading to Windows 8.1, don't panic there is hope.
You may see the Windows Store loading screen stuck in perpetual loop without end.
There is a relatively quick and painless fix.
You may have seen other sites recommend running the WSreset.exe tool, or manually trying to clear the cache from the Windows\SoftwareDistribution\Download folder.
Don't. This can happen when the Store needs to be re-registered after an upgrade.
Open a Command Prompt as an Administrator.
In the Administrator Command Prompt
type or paste the following command:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml
hit Enter.
Now in that same Administrator Command Prompt type or paste: start "" "ms-windows-store:"
Voila. Enjoy installing some new Store apps.
Update 10/2/2014 – I’ve had several users contact me that this also works when testing the Windows 10 Technical Preview which you can get here - Windows 10 Technical Preview
I’ve tested these steps this morning, and they do appear to be the same in Windows 10.