Attempting to open logman.exe on a Windows 2008 server is somehow harder than it looks.
It launches, and then immediately quits without any warning or pop-up. I attempted to "Run as Administrator" but it does the same without any prompt. Is there any way to figure out why it is doing this? Perhaps it is something in my permissions/policy -- how would I go about fixing it or finding out what it is? I've attempted to launch it on multiple machines but the issue still persists.
I am an idiot. You have to open the command prompt, and then run 'logman.exe'. Leaving this up in case anyone else gets brain farts.
Related
As of today my VS Code (ver. 1.69.1) started acting funny.
Yesterday I could open a python script, click "Run without debugging" and the script would run fine.
Today, every time I try to run the script I get no output in the terminal and the start stop relaunch toolbar at the top appears for just a second before disappearing.
As I said, I get no messages, no errors or warnings. Has anyone experienced this too?
Thanks for the help!
Same experience. A regular PC restart didn't help. Then I turned off the PC and after turning it on the problem disappeared! I don't know, I felt like a shaman.
I develop software using Visual Studio 2017 on Windows 10 Home with the latest updates. When my application throws an exception, the executable according to Windows remains open by itself. When I (or Visual Studio) try to delete (overwrite it with newly built executable) Windows says test.exe is open by test.exe and cannot be deleted even though test.exe is not running and there are no other processes that have a handle to test.exe (verified by running Sysinternals handle.exe tool). The only way to deal with this problem is to reboot Windows or log off and log on.
test.exe uses test.dll. If the exception happens in test.dll code, then test.dll will stay locked until reboot.
I did not have this problem on my previous old laptop with the same OS and I don't have it on my work laptop with Windows 10 Pro.
The .net application is a console one written in c#. The content of the code does not matter, it can be just one line that generates any exception. If I run the binary from explorer, I do not experience this problem, only when I run it from the command line. If I kill the main thread test.exe of my test.exe process in sysinternals process explorer before I hit "debug" or "close" button, then I can delete the file without a problem.
It looks like a Windows bug but why I did not have it in my old laptop and my work laptop?
I wonder if anyone else has experience the same problem? Or even better if someone knows how to fix it.
Thanks a lot!
I am running Windows Server 2012 R2 and I am running the program FireDeamon to run my game services, but upon clicking the pop-up message it'll just either bring me to a blue or black screen. I already tried setting the value in the registry to: HKLM\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices=0 and rebooting the machine but this did not work, I even tried it twice.
So is there an clear and working solution for this issue? If not, could someone please provide me with a good working alternative for FireDeamon.
First off, I think I've been to every website and forum there is that's discussing this issue and I've tried many different things. I'm at my wits end. This is the dumbest thing and I just want to start coding again!
I'm using Visual Studio Express 2012 for Windows Desktop. I have a x64 project I'm trying to run in Debug mode using the local windows debugger. The only external library I'm using is that of which is required to run DX11.
I attempt to run my program and it freezes. A window pops up saying "A remote operation is taking longer than expected."
I click Terminate and another window pops up asking if I'd like to terminate the remote session. Why yes, I would.
Then it says, "Unable to start program (my path leading to my .exe). The network connection to the Visual Studio Remote Debugger has been closed."
To my understanding, because Visual Studio itself is a 32 bit application, it needs to use the Remote Debugger to compile to x64. Is that correct?
Regardless, I'm still failing to see where that would break down. I've ran several repairs on VS and upgraded to Service Pack 2 (or 1, whichever is the latest).
I've ran a windows repair and uninstalled any VMWare type stuff on my computer. I'm not using a VPN.
I've even copied msvsmon.exe from my laptop (working instance of the project) over to this computer and still no luck.
I'm about ready to Nuke my OS and do a clean install on everything. sigh
Found the problem. It wasn't Windows Firewall like other threads describe. It was my internet filter. I guess it decided to try and block msvsmon.exe because it was using the network. Adding it, along with WDExpress.exe to the application exceptions list did the trick.
Okay so I have this problem(which strange enough also happens within idea ide) that when I change between workspaces/windows, I suddenly(when changing back to the webstorm editor) can't enter text anymore.
This forces me to restart the application.
Is there a way to fix this without restarting the application each time again?
I have this bug in Ubuntu 13.10.
The workaround I have come up with is to kill ibus-daemon
killall ibus-daemon