Tag Archives: windows

How to fix the issue when your downloads folder takes a long time to open in Windows

Whenever I would open my downloads folder, it would take about 20 seconds to list the files. It only happened on my downloads folder and it was very frustrating.

To fix it, do the steps below.

  1. Right click your download folder (the actual folder, not the shortcut in favourites)
  2. Go to customize
  3. Select documents from the drop down
  4. If documents was already selected, choose “also apply template to all subfolders”

How to see the last logon for a user in Windows

I wanted to see the last time a user had connected to a server that was not on the domain. Use the command below to see the login time, replacing USERNAME with the actual username. This will also work on a domain, but if you have more than one DC you will need to run it on each DC.

net user USERNAME | findstr /B /C:”Last logon”

On a domain joined PC use the command below to find out the last time it logged on to the domain . DO NOT REPLACE THE WORD “DOMAIN” WITH YOUR DOMAIN NAME THOUGH!!

net user USERNAME /DOMAIN| findstr /B /C:”Last logon”

How to fix the "Error: Failed to retrieve directory listing" in Filezilla server

I was using the Filezilla client to connect to a Filezilla server on the LAN the other day, and I could not get a directory listing of the FTP server and I would have the following error “Error: Failed to retrieve directory listing” . I had opened port 21 on the firewall of the FTP server, but still could not get access.

I had to do the steps below, and after this I got access and a directory listing right away.

  • Open Windows Firewall under Control Panel.
  • If using Vista, click “Change Settings”
  • Select the “Exceptions” tab.
  • Click “Add program…”
  • Do NOT select “FileZilla Server Interface” from the list, instead click on “Browse…”
  • Locate the directory you installed FileZilla Server to (normally “C:Program FilesFileZilla Server”)
  • Double click or select “FileZilla server.exe” and press open (Once again, NOT “FileZilla Server Interface.exe”)
  • Select “FileZilla server.exe” from the list and click “Ok”
  • Verify that “FileZilla server.exe” is added to the exceptions list and that it has a check mark in the box next to it
  • Press “Ok” to close the window
  • How to fix the monitoringhost.exe process using 100% cpu.

    I had a few servers that were hitting and sustaining 100% CPU for long periods of time. They were either dual or quad core XEON processors, and the servers normally sat below 10% CPU usage. I ran task manager and found that the monitoringhost.exe process was using all of the CPU cycles, and so i set about researching the issue.

    Monitoringhost.exe is the agent for System Center Operations Manager 2007 that is installed on client systems, and it thankfully has a patch out to fix this issue. Below is the link to the patch on the Microsoft website.

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;954903

    To download the hotfix, you need to enter a valid email address and then Microsoft email you a link to the file and a password to extract the file.

    Download and install this patch to each of the SCOM server and the affected servers and you will not have any issues anymore.

    How to fix issue with Symantec Endpoint client not installing due to a required reboot.

    I had a Windows 2008 server that I was attempting to install the Symantec Endpoint client on, but the client would not install, and the following message was left in the event log:

    Symantec Endpoint Protection (SEP) Installation fails with the following error “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

    I rebooted the server and then tried to install the client again, but the same error would appear.

    I found that there was a registry entry that was giving me grief with the install, and here are the instructions that I used to fix the problem.

    1. Navigate to:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations    
    2. Back up the registry key
    3. Delete the registry key
    4. Install the software without restarting the computer first (Restarting the computer may result in the registry key being placed back in the registry before installation.)
    5. Restore the registry key from the backup location.

     

    NOTE: If you are running  Windows Vista look for this key –  HKEY_LOCAL_MACHINE\SYSTEM\Current\ControlSet001\ControlSessionManager\PendingFileRenameOperations  

    * Thanks to Bill for this Windows Vista suggestion.