I have a Windows 10 64-bit PC (fresh install, not an upgrade).
When I run the setup file (web or offline alike) in order to install Visual Studio (2013 or 2015, Community edition), all I get is a small black rectangle on the screen (which I later found out that this is actually the title of the setup popup window), without the actual window of the installation.
I have tried it also after a reboot, and with various "versions" of the installation files (web, iso, standalone), but it's always the same situation.
What can I do about it? VS is my main development tool and I really need it on this computer as soon as possible.
Similar problem here. Program install ok but display blank screen after launched.
Problem solved when I changed my Nvidia graphics's global 3D setting to integrated graphics.
Right click desktop
Select Nvidia Control Panel
Select Manage 3D Settings
Under preferred graphics processor, select integrated graphics.
Apply.
If you are using a laptop with an external monitor, try unplugging it and using your primary monitor to launch. This worked for me. Laptops often have dual graphics cards and I believe we're hitting some issue with the way the Installer for VS was written (likely WPF)
Once I launced it and started the installation, I could safely plug my monitor in and it kept working properly.
I'm using an AMD GPU, It was a blank white screen but when I hover the mouse over it, I can see the text events
By the way
I went to my AMD Radeon Settings and saw that vs_installershell.exe and vs_setup_bootstrapper.exe were added automatically to the Switchable Graphics list
they were with Not Assigned Option which usually is like High Performace Option
means It would run it with my ATI GPU.
So I clicked on them
Selected Power Saving Option (to work with my Intel GPU)
Which worked and I can see the window of visual studio installer back
after restarting visual studio installer for sure.
whether is your graphics card, just turn on power saving for it.
Had the same issue. Since this topic is not accept any answare, there is one from https://developercommunity.visualstudio.com/content/problem/150888/visual-studio-installer-shows-blank-screen.html
Try to open installer as Admin.
You will probably have blank screen. Do not close it!
Open installer once more.
Hope it help other people with same issue.
the same thing happened to me, i didn't do anything i just waited for it and it started showing it's status, i suggest you close other running programs to avoid conflicts and performance hindering, and try it again.
This seems like a very shoddy issue. I've run into this problem too, and I tested all solutions that I came across online. These all work:
Running the installer as administrator, which is a blank screen. Leave it open and run a second instance of the installer, which will not be blank (doesn't need to be run as administrator the second time.
Changing screen settings so that the laptop screen is not being used.
Downloading the AMD Settings application, and setting vs_installershell.exe to run on powersaving mode. Restart the installer after saving the settings.
Use a default graphics driver instead of the AMD one.
I had the the same problem in my laptop. The temporary solution is: start the installer only without the battery, if installer starts you can connect the cable, it works fine.
I had to run integrated graphics rather than my Nvdia. That solved it for me.
Remember to change it back when programming in OpenGL and DirectX otherwise you may get a list of messages staying that nothing works.
I had the the same problem in my laptop. The work around is, in device management, remove the amd graphics or start the installer only with battery.
I am working with MS Support on a case. We've found that when running an install/update on our application, that it doesn't work as expected on Windows 10.
A window inside our application is returning an error when the Windows Restart Manager sends a WM_QUERYENDSESSION to it. This results in an aborted shutdown on our app during the install.
With the help of Microsoft Support we've determined that it is the "URL Moniker Notification Window". I also know which thread owns the window. But I don't see anything in that code that rings a bell for me.
Where does this window come from? How did I get this in my process?
No answer was ever found. Ultimately, replacement of our installer (w/ WIX) made the world a better place.
I generally use Intel GPA to profile and analyze the rendering process of games on Steam. I wanted to explore Visual Studio's graphics debugger and Nvidia nSight, but I can't get them to "latch" onto the game's process.
This seems to be because of the way steam games are launched. Clicking on the game.exe launches a steam process that in turn launches the game. I don't know why Valve does it this way, but it prevents these tools from "hooking" onto the process and capturing frames.
I tried using the "steam_appid.txt" file to prevent this launch sequence (the steam API mentions this), but to no avail. Just to clarify - I don't have access to the source of these games; i'm just interested in rendering analysis.
I think Nsight can support "latch" you mentioned. Please configure Nsight's User Settings:
Launch external program: $PATH_TO_YOUR_STEAM_EXE
Check the check box named "Application is a launcher" [Here is the key]
Working directory: $PATH_TO_YOUR_STEAM_WORK_DIR
Also remember to uncheck the "Synchronize files" in Synchronization section.
After all configurations have been done, just launch as usual, you will see a Attach dialog box pop out when the steam really runs.
Just run the game from steam, and double click on the game's process in Nsight's Attach dialog box, then you will see the Nsight HUD in the game and every feature for graphic debug of Nsight should works as normal.
The key here is tell Nsight that your 'steam.exe' is just a launcher, and Nsight's dll should hook on the children process from steam.exe, which means "hook/attach on your need".
Thanks
An
I'm running Python 2.7 with ArcGIS Desktop 10.1 on Windows for Server (2 Xeon 2.13 Ghz processors).
Is it possible to suppress or automatically close the dialogue box from Windows that says "python.exe has stopped working" when python crashes? I have a continuously running, multiprocessing script that sometimes crashes for unknown reasons (working on that). When I click to close the crash report window, the script restarts and everything is okay. I want this to happen automatically until I can track down what is causing the crashes.
Thanks very much!
Doug
Procedure for disabling the Windows Debugger dialogue box found here:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204634(v=vs.85).aspx
This prevents the debug dialogue box that requires the user to click [Debug] or [Cancel] if python crashes.
However, there is now another Windows dialogue box that says "python.exe has stopped working. Please close the program" with a button [Close Program]. Sheesh!
The dialog you refer to is part of Windows Error Reporting.
The exact method varies between editions of Windows (Windows 7 instructions here, Google will happily provide for other versions...), but if you disable this feature of Windows, your crashes will happen a lot faster(!).
This is an simply an arcpy bug. You can try to avoid using the steps that are causing the crash, but it generally happens under different tools when used to process through a long list of data.
The only workaround I have found is to make my script save its progress along the way to disk so if you restart the process, it knows where to pickup from.
If you then disable windows debugger message by altering the registry (see below), you can then just repeatedly execute the script in cmd.exe until it completes the entire batch without having to close the process manually every time in between.
I know this is an awful workaround, but it is quite uncommon to have a python library kill off the python interpreter.
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI = "1"
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\Disabled = "1"
I get "Unable to activate Windows Tailored application" error in Metro app when I'm running it under debugger of Visual Studio 11. I installed Windows 8 x64 Developer Preview on my Dell E6510 laptop.
I googled it and found out many people saying it happens when screen resolution is smaller than 800x600 but it's 1920x1280 in my case.
The app itself contains nothing. It's just empty wizard created application which is nothing but windows with black background.
Any ideas? It seems like very common issue.
The solution was quite bizarre but I figured it out.
It turns out not a single Metro application works under Administrator account including my apps. I'm talking about built-in Administrator account that is disabled by default (but which I enabled).
It gives "Access denied" error so I suspect it's somehow related to the way WinRT COM objects were registered or something like that. Go figure.
I hope somebody from Microsoft is reading this.
Best solution is to wait 2 weeks for the next release. The developer preview is full of fun bugs like this. I've seen this error caused by invalid app.xaml. Double check that you really haven't changed anything. I've also seen this error sometimes resolved by rebooting. Have fun!