Problem running VS windows app on windows 8.1

Question

0.00/5 (No votes)

See more:

Hi All

I am having a problem. My VB windows app does not run on a Windows 8.1 machine, although when I debug and run it on the Visual Studio 2015 interface, it runs smoothly. I don't know why it cant run outside the Visual Studio 2015 environment. It runs on Windows 7 but there seems to be a problem in Windows 8.1. When I double click the exe on windows 8.1, its like it loads but never shows on screen.

Any advise friends?

What I have tried:

I googled for a solution, and it showed a possible solution to install Windows 8.1 SDK Kit because it may be missing. So I downloaded and installed it, but it doesnt seem to fix the problem.

Posted 25-Jul-17 21:10pm

kenchidag

Updated 25-Jul-17 22:16pm

OriginalGriff

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2017-07-25T22:16:00

This isn't a problem we can fix: the most likely problem is that it's trying to talk with software (or hardware) that doesn't exist, or is using a different version of a driver.

I'd start by either installing VS on the target machine (in a VM if possible) then running it in the debugger to see what happens, or by adding logging code to the app to try and find out how far it gets before it fails.

But one way or the other, you need to gather information before you can start fixing the problem: at the moment you have nothing concrete to work on.