Forum Widgets
Latest Discussions
Bugs in RAMMAP and ZOOM it, Contig question/improvement
I use the latest versions of Sysinternals' RAMMAP, ZOOM-it and Contig. 1. RAMMAP still contains a bug. Start the program and open the "Process" tab. You will see that RAMMAP truncates the names of the processes to the 1st 14 characters of the process names. If the name of a process is e.g. 30 characters long (including the extension) then RAMMAP only displayes the 1st 14 characters and then the last 16 characters are not shown at all. I brought this bug to the attention of Microsoft in the past but this hasn't been fixed yet. 2. The latest versions of ZOOMit fail to start on my Windows 7 system. It then generates an error. Something along the lines of "Failed to start". This applies to both the 32 bit and 64 bit versions. Previous version of ZOOMit in the past did run & start on my system. 3. Is CONTIG able to defragment directory files themselves ? If so, then what should I type in MSDOS ? These can be fragmented as well. A program called DEFRAGGLER is capable to defrag directory files itself but not CONFIG !!! In Windows MS-DOS one can target the directory itself by using a dot ("."). E.g. "CD c:\windows\." This targets the directory itself. To be added to CONTIG as well in a future version.
RDCMan v3.1: Recent Built-In Group Not Working
I am using Remote Desktop Connection Manager v3.1 (on Windows 11 Enterprise, 24H2) and have found the following two issues... The "Recent" Built-In Group doesn't work...the recently connected servers do not appear in this group (this fails for my colleague too). If you click on the URL shown in the "About" Dialogue box then RDCMan errors and then crashes! (Again, this too fails for my colleague). Many thanks! Lee
Autologon v3.10 fails to set password for Server 2025
When attempting to setup AutoLogon for Windows Server 2025, the AutoAdminLogon, DefaultDomainName, DefaultUserName are all set, though it does not appear to be setting the encrypted password correctly where ever autologon stores that value. I have tested it working successfully on Windows Server 2022.
SYSinternal Help needed
I have TCPview installed and whois with the Microsoft SYSinternal Suite app, and when I right-click to use whois in TCPview my computer gives me an error: Cannot resolve names or use local names. I'm pretty confident my network has been hacked into, and I need this program to work, I've been playing video games between 2 steam accounts where I've been tracked into every match I enter. When I try to run the Whois command prompt it doesn't load.
Two issues with AutoRuns 14.11
Hi, For AutoRuns 14.11: 1. At the folder of C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup I have an .LNK file with link to the patch of Windows Task Manager, C:\Windows\System32\Taskmgr.exe, but it is not shown in AutoRuns at all, mostly not the logon tab and it is not found when you search for it, not even when loading it as admin. Looks like a bug. 2. I also have an object there that is an .LNK file, but it is not linked to an executable, but it is a definition to launch the WhatsApp application, the link is disabled/blocked for a editing, looks something like "5319275A.WhatsAppDesktop_2.2342.7.0_x64__cv1g1gvanyjgm". So AutoRuns naturally marks its line with yellow background an the "Image Path" column states "File not found: .exe", which is technically true, but it will be wiser to consider to not showing a warning, since the object works OK and does launch the app, so it will better to mark it as windows app store object valid object. Thank you.
Loss of default Route when turning on VPN
When I use my FortiClient VPN to connect remotely, Windows loses my local internet connection. I have used an elevated Command Prompt to try and adjust the default route to remedy. Any advice ? Here is the process I am using: Open a cmd window with administrator privileges. You need them to add/delete routes later on. before you connect the vpn execute a "route print" in there and look for the Target "0.0.0.0" - this is your default route. Note down the ip in the column "gateway" there. Connect the vpn and then execute "route print" in the cmd again. You should notice that the gateway (and interface) for the default route has changed. Als note down that gateway ip. Then do a "route delete 0.0.0.0" (I think "route delete default" might do as well but not sure). Then do a "route add 0.0.0.0 MASK 0.0.0.0 <gateway ip you noted down before connecting vpn>" At this point you should regain internet connectivity again. To still be able to reach to your company servers you might have to analogously add a static route to the company subnet with correct subnet mask and the gateway you noted after connecting the vpn. You don't need to enter interface or metric here.
