I have a shortcut to AHK in my Startup folder on a Windows 7 Ultimate x64 machine. Its been working just fine for years. Recently realized it no long loads at startup while everything else in the startup folder works. Once the machine has started, I can go to All Programs -> Startup and click on the AutoHotkey.ahk link and it starts fine.
I've checked Event Viewer and don't see anything there. Even added an exception in my AV, Malware Bytes and Windows Defender which I've never had to do in the past on any PC. I don't remember making any changes on this machine such as a new program install/uninstall.
Any ideas as to what is happening here? I posted this question on the AHK forum but everything suggested there has already been covered.
Thank you
Related
I have a windows batch script that, depending on the user menu selection, opens a powershell.exe and passing a variable to run a .ps1 script. I then use Bat To Exe Converted (v3.0.10) to convert it to an exe. A few hours ago I made changes to the PS script and copied it to the Win'2019 server and it accepted it. Now, I just changed two letters in a write-host message command and it keeps quarantining the file. Since this will be passed to customers I can't be telling them to ignore it or white list it.
I'm guessing the .bat and .ps1 files are throwing Windows Defender off. Funny how it was fine just a few hrs ago. Even if I undo the 2 letters I added it still deleting the exe.
The .bat is quite big and it'd be very difficult for me to convert and add inside the .ps1 script in hope of not setting off the trojan. What other options do I have to fix this? Is there a process or url to notify MS about this to get them to fix this false positive?
NOTE: No other Windows version or 3rd party antivirus that I've tried is detecting the exe infected. Only Win'2019's Defender is.
It looks like MS has fixed the false-positive with my code. I came in to work this morning and tried to copy the exe again and this time it worked. I didn't even contact MS (we don't have a support contract anyway).
Btw the exe consisted of a bat and ps1 script that just downloads some public install files (such as 7zip) from an https address, saves them and when running the exe the user would just get a menu of which of the downloaded programs they want to install.
The issue can be reproduced creating a simple new console application (Language : C++) with Visual Studio 2019 (Community Edition) and then just run program: Ctrl + F5. The solution that worked for me, to run the program, was to add the folder as an exclusion in Windows Defender Antivirus. I couldn't find any solution on other threads
I have this problem going on for few days, every time I open my laptop it starts Windows Powershell automatically.It's not causing me any problem as I close it once it opens, but I am quite annoyed by it and wants to know if this is some problem or just something went bad with my settings. I am using windows 10 pro.
There is probably an autorun entry for Powershell registered on your system. Without more information, it's not possible to tell how it got there.
Programs registering themselves to start up on boot is a common symptom of malware infection, but most malware would also try to hide any visual cues, i.e. the Powershell window would be hidden.
To troubleshoot further, you can try the free utility Autoruns available from Microsoft. Look for any entries related to Powershell.
I have been running jEdit 5.3 for about 1.5 years with no significant problem. On 2017-07-03 I used it and it worked fine. On 2017-07-04, it would not start. jedit and javaw exe's were created, but the jEdit window did not display. I uninstalled version 5.3 and tried to install version 5.4 and got this error:
"The installer will now try to quit a running instance of jEdit.
Please save your work and exit jEdit for the installation to continue."
When I continue, the installer freezes. The same happens if I try to install version 5.3. I did not have a running instance, but the installer thought that I had one. I am guessing that something went wrong with jEdit when I shutdown on the 3rd. (I always intend to close all apps before I shut down, it is possible that I forgot to shutdown jEdit.)
Does anyone know how to tell windows 7 to get rid of this phantom instance of jEdit. I am using a backup version of jEdit 4.5.2 for the time being. So, I can continue with my work. I am guessing that this phantom instance also caused the jEdit 5.3 startup problem that I had before the uninstall.
2017-07-15 Update: I tried installing jEdit 5.4 on Saturday and it worked! On my previous try, when I got the 'running instance' warning I stopped, because every other time I continued at the point the installation froze. On Saturday, I tried continuing after the warning, and it worked! My thanks to Ross Rogers and Mr. Vampire for taking the time to give me expert advice. Renaming the roaming jedit file apparently was effective. I am guessing that deleting the server file would have helped also.
The most likely cause is a stale server file that points to some other process. jEdit and the installer talks to running instances via the network (TCP) on a port that is opened randomly and written to the server file in your settings directory. If you do not quit jEdit cleanly (e. g. only close the window without using the file menu or the shortcut to completely quit jEdit when the jEdit server is running), then jEdit on next start (or the installer) finds the server file and tried to talk to the process listening on the port written in the file. If there is no process listening, it is assumed that the server file is stale and a new instance of jEdit is started. Unfortunately jEdit is not as grateful if there is some process listening on that port but is not answering, jEdit just waits forever currently. This definitely needs to be improved and I think there is also a ticket for this. Try to delete the server file in your settings directory, by default it is %APPDATA%/jEdit/server on Windows and then try to start jEdit or the installer again.
I had to add /SUPPRESSMSGBOXES. /VERYSILENT wasn't silent enough. /? doesn't tell you what the options are.
https://www.itninja.com/software/contributors/jedit-1/4-2570
I'm running this on Windows 7 SP1 with most (if not all) current patches. I have administrative permissions on this machine.
The first time I ran VSCodeSetup.exe, it ran the installer for several minutes then launched the actual application.
I got called into a surprise meeting, so I closed it thinking I'd look at it again later.
However, when I returned to my computer and tried to launch it, I found no evidence that it was actually installed... no desktop icon, no entry in the start menu, no Explorer integration...
I tried running VSCodeSetup.exe again, but all it does it show the installer screen for a split second, which then vanishes.
Since then, I've tried the suggestions outlined in VSCode Installation Failed - Failed to extract installer to install the application, even going so far as to run Update.exe --uninstall followed by running VSCodeSetup.exe again, but nothing has worked.
I even tried disabling my antivirus software and running the installer again, to no avail.
Does anyone know what I can do to get VSCode working again?
According to the comments and answers to Install VSCode in a specific folder, Visual Studio Code installs itself to %LOCALAPPDATA%\Code on Windows.
While I'm not sure why it didn't register itself with Explorer, I can at least create a shortcut to %LOCALAPPDATA%\Code\bin\code.cmd (with icon %LOCALAPPDATA%\Code\app.ico) to get it working again.
Or remove the directory entirely and run VSCodeSetup.exe to install it again, which still doesn't add Explorer integration... but this time at least the PATH now has code in it.
On windows VSCode is installed as Code.exe and its located in your
C:\Users\<windows-user>\AppData\Local\Code\app-<version-number>\Code.exe
or
C:\Users\John\AppData\Local\Code\app-0.5.0\Code.exe
I'm following these instructions to remotely debug a python script http://pydev.org/manual_adv_remote_debugger.html
Using breakpoints and stepping work without a problem, but after resuming the script (without any other further breakpoints) the script executes the remaining instructions, and then hangs instead of exiting normally. Even closing the server from pydev does not help, I have to Ctrl+Break the script
I am sure I've done this a while ago with an older eclipse+pydev, and the script resumed and exited normally (and it's very important for me not to mess the rest of the execution).
I've tried this with both Eclipse Luna and Liclipse pydev_4.0.0.201504132356, pydev_4.0.0.201504092214 on Windows 7 x64, same behaviour
Is this an intended behavior or a bug? How could I make pydev let the script end normally?
I can't reproduce this here... please report that as a bug adding details on how to reproduce it (i.e.: ideally, create a project on github and add a step-by-step on how to reproduce it so that it can be fixed... without being able to reproduce it properly, it may be pretty hard to fix).
Also, please give details on the OS and Python version used in the report (https://sw-brainwy.rhcloud.com/tracker/PyDev/)