Skip to content

Neither Stable nor Canary work on Windows Server 2012 R2 #4641

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Sojaner opened this issue Jun 4, 2018 · 5 comments
Closed

Neither Stable nor Canary work on Windows Server 2012 R2 #4641

Sojaner opened this issue Jun 4, 2018 · 5 comments
Assignees
Labels

Comments

@Sojaner
Copy link

Sojaner commented Jun 4, 2018

Please read through the guidelines before creating a new issue.

Describe the bug
As soon as the installation is done, the app's screen stays either black or light orange (or white it is) and the cursor constantly turn into arrow+sandwatch for a glitch and back to arrow again.
The UI never appears.

To Reproduce
Steps to reproduce the behavior:

  1. Download version 6.1.3 x64/Latest Canary build on Windows Server 2012 R2 x64
  2. Install
  3. Run

Expected behavior
Can see the UI and interact correctly.

Screenshots
capture

App information (please complete the following information):

  • Postman Version 6.1.3 x64
  • OS: Windows Server 2012 R2 x64
@thecuriousdev
Copy link

Hey @Sojaner, thanks for reporting this issue. You found this issue after the 6.1.3 update or its been there always?

This may be related to a known issue where Postman doesn’t launch with certain GPUs. A workaround for this issue involves disabling your GPU, and detailed instructions on how to do that can be found via the link below.

#4594

@Sojaner
Copy link
Author

Sojaner commented Jun 4, 2018

It appeared after the 6.1.3 update @thecuriousdev. I had been using the Postman for a long time.
And it's right when I'm in a super tight deadline for releasing a web api project. :(

@thecuriousdev
Copy link

@Sojaner I am very sorry about that :( , Have you tried the work around mentioned in #4594?

@Sojaner
Copy link
Author

Sojaner commented Jun 5, 2018

Thanks for the workaround @thecuriousdev. Seems to be working again. Wish I had it 2 days ago. :)

@thecuriousdev
Copy link

thecuriousdev commented Jun 6, 2018

@Sojaner good to hear that :), I am closing this ticket, we'll track the progress of this issue in #4594

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants