I'm trying to run a legacy VB6 application on Windows 10. I'm using creating an .sdb shim file which detects the application's .exe using the Compatibility Administrator tool found in the Windows ADK. Whenever the .exe runs, the screen resolution is resized to a specific resolution. When the .exe stops, the resolution returns to normal.
The Compatibility fixes I'm using are "ForceDisplayMode" with parameters to display at the legacy app's old resolution. And also "ForceTemporaryModeChange" which will revert the screen resolution back to normal.
One problem I'm having is that when the application is open, if I close my laptop lid and reopen it, the .sdb stops working (windows doesn't log out). If I log out, the old resolution is maintained as expected. I'm trying to figure out if there's an option to maintain the .sdb's resolution, or if this is an oversight on Microsoft's end?
Ok, in the off chance that anyone has this incredibly obscure problem in the future, the solution was apparently to disable tablet mode on Windows 10 1809. That solves the .sdb shim being undone by closing the lid on my SP3/SP6s.
Edit: Ok, turns out that was not the solution. It was just coincidence, so I've uncheckmarked this answer. We had an image that didn't have this problem but then later images reverted this behavior. Still don't know why this occurs.
Edit 2: I still don't know why this occurs but I have a few observations that may help someone. I'm on Windows 10 LTSC Version 1809 Build 17763.615. It seems to have to do with specifically putting the SP6 to sleep via flipping up the keyboard. If you sleep by Windows > Power > Sleep or pressing the power button or letting the SP6 go to sleep on its own, the SDB is correctly maintained. Another odd observation is that if you sleep via the 3 ways listed above but then flip up the keyboard, the SDB is cancelled.
Related
Relatively new to intermediate level Windows user here. I recently installed a game which kept restarting (automatically) every few seconds even after I closed it every few seconds. Windows (I use Windows 8.1) kept trying to open the .exe even after I uninstalled. I tried deleting a couple of registry entries of it (I guess I deleted a dll registry related to it)
After deleting a couple of registry entries
but it still keeps trying to open it. What can I do about it?
These guys keep coming up as I close them
Currently doing a CS course. This is my first question on stack overflow!
EDIT: This window keeps popping up every few seconds. (I have uninstalled it)This one. The game is Battlezone(1998) from Microsoft which itself is legit. I found it on a really old CD which I found in my house recently and I just installed it. It is clear on Avast Antivirus. Nothing suspicious there in Task Manager or in Startup
Try using the Taskmanager to stop any process that is related to that programm.
If you have uninstalled it and the programm still starts it probably is still installed -> the .exe file hides somewhere.
Try find and delete it manually.
You can check if you have a system tray icon as well, some programms don't close if you close them but minimize into a system tray icon. These can often be closed using right click -> close.
Does the programm start automatically after pc start? -> check your autostart folder and the autostart tab of your taskmanager and remove it.
Anymore stuff you can provide us with? -> which game, screenshots, you sure it's not maleware?
I currently run a 64bit Windows 10 development box. I have old VB6 source that I have to unfortunately keep updated for the time being. For some reason all the sudden I noticed that one of the applications I have just built seemed to stay running in the background after the GUI was closed.
I started debugging the issue more and more until I found out that the only time it would seem to persistently stay open in the background after the GUI was closed was if I clicked the button on my form that would call the Common Dialog control to show the file open GUI. I only have to show the file open window and then hit cancel for this to happen.
This ONLY seems to happen on ONE of my dev machines (not the other). Every time I use that CD file open box I have to open task manager up and end the task. I also tried to make sure all forms were closed when my main form starts to Unload. Nothing seems to work or shed any clue on what the issue is. I have also double checked that the following files are now all the same coping them from the known working dev machine to my broken one and re-registering them.
COMDLG32.OCX
comdlg32.oca
comdlg32.dll
COMDLG32.DEP
Both machines are running the same exact OS Win10 Pro 64bit.
That does sound strange, getting different results on the two machines. Pragmatically, you can work around the problem (without actually understanding it) by making sure that you execute an End statement. (You can put it in the QueryUnload event to make sure it's hit if the user clicks the "X".)
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.
This issue is driving me crazy. I'm on a corporately controlled network but have local administrator rights. This issue is happening with all versions of Visual Studio installer where you initiate the install, then you see the initial splash screen and then that vanishes and it looks like nothing is there. But if you click and drag that area you can see the window borders during the drag. Some portions of the invisible window even respond to mouse clicks. There's even a task bar indication that is blank when you hover over it. I can't even update the current 2013 installation to SP5 because even that window behaves the same way.
However, it just totally hangs the install and since I can't see the install options I don't know if there's a failure or it's just waiting on me to do something.
I've seen several posts about this outside of here but all of them lead to a dead-end.
I have installed Studio on this machine before - actually all versions since 2005 and never have seen this issue until it started about 2 months ago. I did updates galore and all that. Updated my video drivers, blah, blah, blah. I've even tried remoting into this this box and seeing if that would alter the display enough to see what is going on...all to no avail.
The box is beefy (i5, 16GB, 500GB SSD...triple display, etc...) so it more than meets the requirements.
When I try to install any version of Visual Studio, the install window briefly appears and then disappears. However, it is still there, just 100% transparent. Has anyone else seen this before?
I was able to finally find an answer to the invisible install dialog question, it is however not an adequate solution, but an answer. I have to run only one monitor then the install dialog is visible and things proceed normally.
My solution was to disable the graphics card I have on my computer and run on onboard graphics card. It seems that the issue is with the graphics, so forcing the system to use the "regular" graphics card did the trick.
I have to use /Full /Passive from the command line to install on a build server. I would prefer less flashy installer for a more robust one. I am sure its a combination of the graphics card etc. But other installers work.
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"