Skip to main content

Windows 10 Start Apps in Full Screen


Launch Windows 10 apps in in full screen mode

If you recently have installed the Windows 10 Technical Preview on a tablet or computer system, you may have noticed that Windows Store apps run on the desktop now if you are using a system with mouse and keyboard.
I installed Windows 10 on my Surface pro one, but haven't seen any report saying the other models behave differently.
While it is still possible to enable the Start Screen interface, instead of using the Start Menu as you cannot use both it seems, apps that you run will run in Windows desktop mode by default.
That's not a big problem most of the time, but if you prefer to run some apps in full screen, Netflix or a game for example to get that extra bit of screen space this way, then you may have wondered how to make that happen.
There is no full screen option when you look at the window control icons in the top right corner of the screen. While you can use the controls to maximize the app window, it is still running in a window and not full screen.

To view an App in full screen mode simply select the tree dots in the left cornor of the App. Here you will see a few options:
Selecting the Full Screen option will display the App in full screen mode. To exit the full screen mode simply push the windows button.

I have not found any way to have all Apps automatically start in full screen mode. But I suppose the RTM release of Windows 10 will detect what device you are on (tablet/laptop/PC) and display the best setting for you.

Comments

Popular posts from this blog

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.


PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated.

Problem: If you for example run the Test-SPsite command you might see something like the following:


Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd, …