Answered by:
Launching Windows Store App in VS2013

Question
-
I try to start a default Windows Store App and get the error:
System.Runtime.InteropServices.COMException
(Exception from HRESULT: 0x8027025B)I have the developer licence
What could be the reason of the error?
Thank you
Tuesday, November 11, 2014 11:25 AM
Answers
-
Hello GagAlex63,
According to the thread at [1], it seems that there're some problems with the local firewall. What you can try is to run Visual Studio as Administrator or temporarily turn off the firewall. Sometimes rebuilding the solution also helps.
Regards,
Bo Liu
Developer-Hotline for MSDN Online Germany
Disclaimer:
Please take into consideration, that further inquiries cannot or will be answered with delay.
For further information please contact us per telephone through the MSDN-Entwickler-Hotline: http://www.msdn-online.de/Hotline
For this post by the MSDN-Entwickler-Hotline the following terms and conditions apply: Trademarks, Privacy as well as the separate terms of use for the MSDN-Entwickler-Hotline.- Marked as answer by Jamles HezModerator Wednesday, November 26, 2014 10:01 AM
Tuesday, November 11, 2014 1:32 PM -
Hi GagAlex63,
Possible, looks like a privilege or group policy issue.
Probably some part of code might need admin permission, could you ask your network owner add you to the local administrator group?
--James
<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support
Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.- Marked as answer by Jamles HezModerator Wednesday, November 26, 2014 10:02 AM
Wednesday, November 19, 2014 9:28 AMModerator
All replies
-
Hello GagAlex63,
According to the thread at [1], it seems that there're some problems with the local firewall. What you can try is to run Visual Studio as Administrator or temporarily turn off the firewall. Sometimes rebuilding the solution also helps.
Regards,
Bo Liu
Developer-Hotline for MSDN Online Germany
Disclaimer:
Please take into consideration, that further inquiries cannot or will be answered with delay.
For further information please contact us per telephone through the MSDN-Entwickler-Hotline: http://www.msdn-online.de/Hotline
For this post by the MSDN-Entwickler-Hotline the following terms and conditions apply: Trademarks, Privacy as well as the separate terms of use for the MSDN-Entwickler-Hotline.- Marked as answer by Jamles HezModerator Wednesday, November 26, 2014 10:01 AM
Tuesday, November 11, 2014 1:32 PM -
Also please make sure you have installed the latest update VS 2013 update 3.Tuesday, November 11, 2014 6:20 PMModerator
-
Thank you for replay!
I have reasons to think that the problem is in domain group politics. Everything is OK on local computers.
But it does not work in domain.
Wednesday, November 12, 2014 12:59 PM -
Hi GagAlex63,
Possible, looks like a privilege or group policy issue.
Probably some part of code might need admin permission, could you ask your network owner add you to the local administrator group?
--James
<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support
Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.- Marked as answer by Jamles HezModerator Wednesday, November 26, 2014 10:02 AM
Wednesday, November 19, 2014 9:28 AMModerator