Quantcast
Channel: GlobalSCAPE Knowledge Base
Viewing all 785 articles
Browse latest View live

"Upload using CuteFTP Pro" on the Windows Explorer right-click menu not available on Windows 7, 64-bit OS

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® version 8

SYMPTOM

"Upload using CuteFTP Pro" on the Windows Explorer right-click menu is not available on a Windows 7 64-bit operating system.

RESOLUTION/WORKAROUND

Open CuteFTP, log in to your FTP site, then click and drag the file from Windows Explorer to the remote directory in CuteFTP.

MORE INFORMATION

On Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista, and Windows 7, 32-bit operating systems, you can create a submenu option in Windows Explorer that will allow you to right-click a file to upload it with CuteFTP. The submenu provides options to connect to a site using the Connection Wizard or sites that you have defined in CuteFTP.

For more information, refer to Adding CuteFTP to the Windows Explorer Right-Click Menu in the CuteFTP online help.


The registered user name shown in the About box is incorrect.

$
0
0
THE INFORMATION IN THIS ARTICLE APPLIES TO:
  • CuteFTP Pro®, Home, and Lite, version 8
PROBLEM

The registered user name shown in the About box is incorrect or it has become corrupted.

RESOLUTION

If the registered user name shown in the About box is incorrect or has been corrupted, delete the file named value.dat from the following location. After deleting value.dat, restart CuteFTP and then use your existing registration serial number to activate and register CuteFTP again.

In Windows XP:

C:\Documents and Settings\All Users\Application Data\GlobalSCAPE\CuteFTP 8 [Home or Professional]\value.dat

In Windows Vista and Windows 7:

C:\Program Data\GlobalSCAPE\CuteFTP 8 [Home or Professional]\value.dat

IF value.dat IS HIDDEN...

By default, Windows hides many program files to prevent accidentally deleting or changing them. If you cannot find value.dat at the path shown above, follow the steps below (depending on your operating system) to display hidden files and folders.

In Windows XP:

  1. Click Start, click Control Panel and then double-click Folder Options.
  2. On the View tab, under Hidden files and folders, click Show hidden files and folders and then click OK.

In Windows Vista:

  1. Click Start, click Control Panel, click Appearance and Personalization and then click Folder Options.
  2. On the View tab, under Hidden files and folders, click Show hidden files and folders and then click OK.

In Windows 7:

  1. Click Start, click Control Panel, and then click Folder Options.
  2. On the View tab, under Hidden files and folders, click Show hidden files and folders and then click OK.

One or more options missing from the Folder Tools submenu; in its place is No plug-in tools, which appears dimmed (grayed out)

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® and Home, all versions

SYMPTOM

One or more options missing from the Folder Tools submenu; in its place is No plug-in tools, which appears dimmed (grayed out).

RESOLUTION

To resolve this issue

  1. Exit CuteFTP, if it is running and stop the Transfer Engine (TE):
    1. CTRL+ALT+DELETE, then click Start Task Manager.
    2. On the Processes tab, click "ftpte.exe," then click End Process.
  2. So that you don't lose your Site connection data, find the sm.dat file and copy it to a location where you can easily find it, such as your desktop.
    • In Windows XP, the default location is C:\Documents and Settings\USERNAME\(show hidden files) Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\Version#.
    • In Windows Vista and Windows 7, the default location is C:\Users\Your User Name\AppData(You will need to show the hidden files)\Roaming\GlobalSCAPE \CuteFTP\Version#.
  3. Uninstall CuteFTP using Window's Add and Remove Programs tool:
    1. Click Start > Run > appwiz.cpl.
    2. Right-click CuteFTP, then click Uninstall.
    3. In the InstallShield wizard, click Remove.
  4. After CuteFTP is removed, remove the CuteFTP folder in C:\Documents and Settings\USERNAME\(show hidden files) Application Data\GlobalSCAPE\.
  5. Ensure that the CuteFTP folder is also deleted from C:\Program Files\GlobalSCAPE.
  6. Empty the Recycle bin and then restart the computer.
  7. Your computer should now be completely clear of all versions of CuteFTP that you had installed. Now you can download CuteFTP from the following link and install it using your serial number: http://www.globalscape.com/support/reg.aspx (Be sure to download the version for which you have a license. If you plan to upgrade, install your licensed version first.)
  8. After you install CuteFTP, import the Site Manager data (sm.dat) file that you saved in step 2 above.
    1. Click Tools > Site Manager > Import/Export FTP Sites.
    2. In the Import/Export wizard, click Import, then click Next.
    3. In the drop-down list, click CuteFTP 4.0-6.0 (sm.dat), then click Next.
    4. Follow the remaining prompts in the wizard to complete the import.
  9. Configure CuteFTP's Global Options (Log, Proxy, Security, Transfer, Navigation, and Display settings), if necessary.
  10. Attempt to connect to your FTP site to verify that installation and configuration is complete.

MORE INFORMATION

Refer to the following online help topics for more information:

ERROR:> Can't read from data socket. Socket error = #0

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP® (all versions)

SYMPTOM

When trying to transfer files, an error appears:

ERROR:> Can't read from data socket. Socket error = #0

Other (non-CuteFTP) symptoms include:

  • Anti-virus software failed to update (cannot connect to server)
  • Microsoft update fails
  • Cannot run regedit or cmd
  • Certain Google searches are redirected to other ad pages

RESOLUTION

The error is unrelated to CuteFTP, but appears to be a malware virus that prevents programs from using the data socket.

To resolve this issue, you will need to edit the Windows Registry.

Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk. It is a good practice to back up (export a copy of) the registry before you make any changes to it. For more information about editing the Windows Registry, refer to Knowledge Base article Q10411 - HOWTO: Windows Registry Settings.

To resolve the issue:

  1. Search for the file regedit.exe or regedit32.exe (e.g., in C:\WINDOWS\system32) and make a copy of it on your desktop.

  2. Rename the copy whatever.exe. (The malware is actually monitoring files with specific names, preventing them from running. Renaming targeted files will prevent them from being "seen" by the malware.)

  3. Run whatever.exe to open the registry and search for the following registry key:

    HKLM/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/Drivers32/aux2

  4. Delete this key!

  5. Restart the computer.

  6. You can now delete whatever.exe.

Special thanks to egaille from the CuteFTP user forum who shared this information from http://freeforum.avg.com/read.php?12,183533,backpage=3,sv.1!

Remote pane missing Minimize, Restore and Close buttons.

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® versions 8.0.0 thru 8.0.7 when running on Windows Vista

SYMPTOMS

When using a Windows Vista theme and connected with a remote site (or when editing a file), the remote pane is missing the Minimize, Restore and Close buttons normally displayed at the top right of the remote pane. This behavior occurs only when using a Windows Vista theme.

CAUSE

This error is caused by an incompatibility between CuteFTP 8.0.x and Windows Vista. This behavior occurs only when using a Windows Vista theme. This issue was fixed in CuteFTP 8.1.

RESOLUTION

To resolve this issue, update CuteFTP to version 8.1 or greater.

CuteFTPPro.TEConnection error when attempting to run a script (Evaluation Period Expired).

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP 8 Pro®, version 8.0.6 only

SYMPTOMS

When attempting to run a script, the following error is encountered:

This can occur even when CuteFTP Pro is fully activated and registered.

CAUSE

This problem is in CuteFTP Pro 8.0.6 only.

RESOLUTION

This issue was fixed. Upgrade to CuteFTP Pro 8.0.7 or greater. Registered users can download the most current version of CuteFTP from the Replacement Software Downloads Web page.

CuteFTP File Transfer Application has stopped working

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® and Home versions 8.0.0 thru 8.0.5 when running on Windows Vista

SYMPTOMS

When running CuteFTP on Windows Vista, the following error may occur when closing the program: CuteFTP File Transfer Application has stopped working.

CAUSE

This error is caused by an incompatibility between CuteFTP (versions 8.0.0 - 8.0.5 only) and Windows Vista. The error message may be safely closed without affecting the use of CuteFTP or Windows Vista. This issue was fixed in CuteFTP 8.0.6.

RESOLUTION

Users should update to CuteFTP 8.0.6 or above. To find out which version of CuteFTP is installed on your computer, start CuteFTP and then open the Help menu and click About CuteFTP.

The most current version is available for download on the Replacement Software Downloads page.

Lockstep Folder Navigation Quit Functioning in CuteFTP Pro®

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro®, versions 7.x and 8.x

SYMPTOMS

Lockstep folder navigation suddenly stops/starts working.

CAUSE

The Lockstep Folder Navigation icon was inadvertently clicked.

RESOLUTION

Toggle the Lockstep Folder Navigation icon, or on the main menu, click Tools, then click Lockstep Navigation.


HTTP Status and Error Codes

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • All GlobalSCAPE products, all versions

DISCUSSION

During your HTTP sessions, you'll receive various numbered codes from Web servers. When connected via HTTP, CuteFTP displays these codes in the log window. Some codes represent errors. Most others simply communicate the status of the connection. Here are brief explanations for the most common status and error codes.

The list below are standard HTTP codes. Numbers outside this list are proprietary to the Server or Client that you are using.

Error or Status Code Description

100 Series

Informational - These status codes indicate a provisional response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.

100

Continue.

101

Switching protocols.

200 Series

Success - This class of status codes indicates that the server successfully accepted the client request.

200

The client request has succeeded. This status code indicates that the Web server has successfully processed the request.

201

Created.

202

Accepted.

203

Non-authoritative information.

204

No content.

205

Reset content.

206

Partial content.

300 Series

Redirection - The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server.

302

Object moved.

304

Not modified. The client requests a document that is already in its cache and the document has not been modified since it was cached. The client uses the cached copy of the document, instead of downloading it from the server

307

Temporary redirect.

400 Series

Client Error - An error occurs, and the client appears to be at fault. For example, the client may request a page that does not exist, or the client may not provide valid authentication information.

400

Bad request.

401

Access denied.

401.1

Logon failed. The logon attempt is unsuccessful, probably because of a user name or password that is not valid.

401.2

Logon failed due to server configuration.

401.3

Unauthorized due to ACL on resource. This indicates a problem with NTFS permissions. This error may occur even if the permissions are correct for the file that you are trying to access. For example, you see this error if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory.

401.4

Authorization failed by filter.

401.5

Authorization failed by ISAPI/CGI application.

401.7

Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0.

403

Forbidden.

403.1

Execute access forbidden. The following are two common causes of this error message:

  • You do not have enough Execute permissions. For example, you may receive this error message if you try to access an ASP page in a directory where permissions are set to None, or you try to execute a CGI script in a directory with Scripts Only permissions.
  • The script mapping for the file type that you are trying to execute is not set up to recognize the verb that you are using (for example, GET or POST).

403.2

Read access forbidden. Verify that you have Read access to the directory. Also, if you are using a default document, verify that the document exists.

403.3

Write access forbidden. Verify that you have Write access to the directory

403.4

SSL required. Use HTTPS instead of HTTP to access the page.

403.5

SSL 128 required.

403.6

IP address rejected.

403.7

Client certificate required. You do not have a valid client certificate installed

403.8

Site access denied.

403.9

Too many users. The number of users who are connected to the server exceeds the connection limit.

403.10

Invalid configuration.

403.11

Password change.

403.12

Mapper denied access. The page that you want to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file.

403.13

Client certificate revoked.

403.14

Directory listing denied.

403.15

Client Access Licenses exceeded.

403.16

Client certificate is untrusted or invalid.

403.17

Client certificate has expired or is not yet valid.

403.18

Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.

403.19

Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.

403.20

Passport logon failed. This error code is specific to IIS 6.0.

404

Not found. This error may occur if the file that you are trying to access has been moved or deleted.

404.0

File or directory not found.

404.1

Web site not accessible on the requested port.

404.2

Web service extension lockdown policy prevents this request.

404.3

MIME map policy prevents this request.

405

HTTP verb used to access this page is not allowed (method not allowed).

406

Client browser does not accept the MIME type of the requested page.

407

Proxy authentication required.

412

Precondition failed.

413

Request entity too large.

414

Request-URL too long.

415

Unsupported media type.

416

Requested range not satisfiable.

417

Execution failed.

423

Locked error.

500 Series

Server Error - The server cannot complete the request because it encounters an error.

500

Internal server error. You see this error message for a wide variety of server-side errors.

500.12

Application is busy restarting on the Web server. Indicates that you tried to load an ASP page while IIS was in the process of restarting the application. This message should disappear when you refresh the page. If you refresh the page and the message appears again, it may be caused by antivirus software that is scanning your Global.asa file.

500.13

Web server is too busy.

500.15

Direct requests for Global.asa are not allowed.

500.16

UNC authorization credentials incorrect. This error code is specific to IIS 6.0.

500.18

URL authorization store cannot be opened. This error code is specific to IIS 6.0.

500.100

Internal ASP error. You receive this error message when you try to load an ASP page that has errors in the code.

501

Header values specify a configuration that is not implemented.

502

Bad Gateway. Web server received an invalid response while acting as a gateway or proxy. You receive this error message when you try to run a CGI script that does not return a valid set of HTTP headers.

502.1

CGI application timeout.

502.2

Error in CGI application.

503

Service unavailable. This error code is specific to IIS 6.0.

504

Gateway timeout.

505

HTTP version not supported.

Can CuteFTP® be installed onto a USB drive or other storage device?

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® and Home for Windows (All Versions)

QUESTION

Can CuteFTP be installed onto a USB drive or other storage device?

ANSWER

CuteFTP can be installed onto a USB or thumb drive; however, registration details and most settings are stored in the registry so they are not portable.

Additionally, if you install onto a storage device then you must purchase an additional license for each separate computer on which the Software is used or accessed.

Is CuteFTP compatible with Windows XP Professional x64 Edition?

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® and Home (All Versions)

QUESTION

Is CuteFTP compatible with Windows XP Professional x64 Edition?

ANSWER

As a 32-bit program, CuteFTP was not written specifically for Windows XP Professional x64 Edition, however, customers have run it without problems.

Using CuteFTP behind a router

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® (All Versions)

DISCUSSION

In most cases, CuteFTP does not have any problems working behind a router. If you are having problems, try doing all your transfers in PASV mode.

If connections or transfers still fail:

  1. Check with the FTP server administrator to make certain the Server and it's network are configured to allow FTP in PASV mode.
  2. Check your router documentation for information on how to set it up for FTP, or how to open the appropriate ports. FTP generally uses port 21.
  3. You can define a port range for CuteFTP to operate with under Tools > Global Options > Connection > Assign PORT mode IP address and port range.
  4. You can try using UPnP (if your NAT or router supports it) to establish a connection properly. You can turn on port mapping under the Tools > Global Options > Connection tab.

Configuration notes

  • To perform transfers in PORT mode, or for secure transfers, refer to your router's documentation for information on how to configure the router for such transfers.
  • If you are behind a NAT firewall, and the Secure FTP server is on a different network, you can only make data transfers in PORT mode using a Clear Command Channel SSL connection.

"Enter FTP Command" is unavailable

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro®, Home, and Lite

SYMPTOM

On the Tools menu, Enter FTP Command is grayed out and unavailable.

RESOLUTION

When you are connected to the remote site, click inside the remote pane on the right side of the screen so that the remote side is selected or active. With the remote site selected, the command becomes available.

CuteFTP support for Japanese or Chinese characters in file names

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® all versions

QUESTION

Question: Does CuteFTP support Japanese/Chinese (Kanji) characters in file names?

ANSWER

Yes, as long as you have the relevant language pack installed for the operating system. This would allow for the Japanese or Chinese characters in the file system. It is not necessary to select the language, but you need the pack installed to show (or save/modify) files to the file system with those characters in it.

Shell is not connected to the TE

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro®, Home, and Lite

SYMPTOM

When attempting to start CuteFTP, the following error appears: Shell is not connected to the TE.

RESOLUTION

This error can occur if the CuteFTP Transfer Engine (TE) becomes disassociated with the CuteFTP interface.

To associate the two components, follow these steps:

1. Navigate to the folder where the CuteFTP TE is installed. By default, this is C:\Program Files\GlobalSCAPE\CuteFTP Home (or Professional)\

2. Double-click the file named ftpte.exe to start the TE by itself.

3. While the TE is open, start CuteFTP normally via the Start menu.

At this point, the association will have been accomplished and you can resume using the software normally.

If you continue to get the same error, then it may be necessary to reinstall CuteFTP. You can download the latest version or build of CuteFTP from here:
http://www.globalscape.com/support/reg.asp

After downloading, run setup and select the REPAIR option.


Cannot Load advert.dll / Cannot Initialize Advertising System in CuteFTP

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP 3.0
  • CuteFTP 3.5
  • CuteFTP 4.0

SYMPTOM

When starting CuteFTP, the following error is encountered:

Cannot Load advert.dll

or

Cannot Initialize Advertising System

RESOLUTION

To repair the problem, re-install CuteFTP. If you are currently using CuteFTP version 3.0, 3.5 or 4.0 then download and install the free upgrade to CuteFTP 4.2 from this page:
http://www.globalscape.com/support/reg.asp

CAUSE

Some older versions of CuteFTP used advertising banners in the evaluation versions. One or more of the necessary components is no longer present on your system.

CuteFTP was unable to load the resource file

$
0
0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro® and Home (All versions)

SYMPTOMS

When starting CuteFTP from the Quick Launch toolbar, the following error occurs:

CuteFTP was unable to load the resource file. Please reinstall CuteFTP and repair. If you continue to receive this error, please contact our support department.

    Reinstalling the program does not resolve the error.

    RESOLUTION

    To repair the problem, remove CuteFTP from the Quick Launch toolbar and then create a shortcut on the toolbar instead.

    CAUSE

    This error can occur if the CuteFTP program file is copied to the Quick Launch toolbar. Instead, a shortcut to the program should be created.

    Moving CuteFTP to a new computer

    $
    0
    0

    THE INFORMATION IN THIS ARTICLE APPLIES TO:

    • CuteFTP Pro® and Home (Most versions)

    DISCUSSION

    Use one of the following methods to move the CuteFTP® software to a new computer:

    OPTION 1 (If the old computer is no longer running or available to you, or if you do not need the existing Site Manager data):

    1. Download the software from this page: http://www.globalscape.com/support/reg.aspx
    2. Install CuteFTP on the new computer and register it using your existing serial number.

    OPTION 2 (If the old computer is still available to you and you need access to the existing Site Manager data.):

    ON THE OLD COMPUTER:

    1. Launch CuteFTP. If you do not already have your registration serial number available, on the Help menu click About CuteFTP. Record your serial number so that it is available to be used on the new computer.
    2. On the Help menu, click Backup registration & personal data then click Browse. Select a drive with portable media (e.g., a USB drive) or network location in which to save the data, then click OK. A backup successful message appears when completed.
    3. If you are transferring the license to the new computer, remove the software from the old computer using Windows Add or Remove Programs in the Control Panel.

    ON THE NEW COMPUTER:

    1. Download the software from this page:
      http://www.globalscape.com/support/reg.aspx
    2. Install CuteFTP on the new computer and register it using your existing serial number.
    3. Insert the media on which your backup was saved or make sure you have access to the network location in Step 2 above.
    4. Launch CuteFTP. On the Tools menu, click Site Manager then click Import FTP Sites and follow the prompts in the wizard. Note: On some older versions of CuteFTP, all you need to do is open the Site Manager and then click Import. If you need more specific instructions about how to import your Site Manager data, refer to Importing sites in the Site Manager.

    WHERE ARE MY SITES?

    The sites in the Site Manager are stored in a file called sm.dat. The location in which sm.dat is stored depends on your version of Windows.
    IMPORTANT: sm.dat is not a "human-readable" file; you can't just type your site information into a text file. Manually editing the sm.dat file can corrupt it and you will lose your site information.

    • Windows XP: C:\Documents and Settings\USERNAME\Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\VERSION\SM.DAT
    • Windows Vista: C:\ProgramData\GlobalSCAPE\CuteFTP 8 [Home/Professional]\
    • Windows 7: C:\Users\USERNAME\Application Data\Roaming\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\8.0\SM.DAT

    (You may need to select "View hidden files and folders" on the View tab in Folder Options.)

    How do I backup/restore my scheduled uploads?

    $
    0
    0

    THE INFORMATION IN THIS ARTICLE APPLIES TO:

    • CuteFTP Pro®, all versions

    QUESTION

    How do I backup/restore my scheduled uploads?

    ANSWER

    Scheduled uploads and all of the data in the queue window is stored in a file named CIS_Queue.dat, which is located in the same directory as sm.dat.

    The location in which CuteFTP's data files are stored depends on your version of Windows:

    • Windows XP: C:\Documents and Settings\USERNAME\Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\VERSION\SM.DAT
    • Windows Vista: C:\ProgramData\GlobalSCAPE\CuteFTP 8 [Home/Professional]\
    • Windows 7: C:\Users\USERNAME\Application Data\Roaming\GlobalSCAPE\CuteFTP Pro\8.0\SM.DAT

    (You may need to select "View hidden files and folders" on the View tab in Folder Options.)

    For the procedure for backing up files, refer to Backing Up Site Configurations.

    Remote files and folders not visible (Files not parsed)

    $
    0
    0

    THE INFORMATION IN THIS ARTICLE APPLIES TO:

    • CuteFTP Pro,® Home, and Lite, version 8.3.3.x and earlier

    SYMPTOMS

    When connected to an FTP server which identifies itself as running on Windows NT (e.g., IIS running on Windows Server 2008) the list of remote files and folders is not visible in the remote pane. Additionally, the CuteFTP connection log contains lines similar to the following example:

    STATUS:> [4/12/2010 3:03:41 PM] 06-09-2009 09:26AM 1119 examplefile1.asp<<< NOT PARSED

    STATUS:> [4/12/2010 3:03:41 PM] 04-12-2010 06:44PM 1100 examplefile2.php<<< NOT PARSED

    STATUS:> [4/12/2010 3:03:41 PM] 09-04-2009 03:12PM 1442 examplefile3.htm<<< NOT PARSED

    STATUS:> [4/12/2010 3:03:41 PM] 06-09-2009 09:26AM 1800 examplefile4.txt<<< NOT PARSED

    RESOLUTION

    To resolve this issue, upgrade to CuteFTP version 8.3.4 or later. You can download the most recent release version of CuteFTP from the Replacement Software Download Page.

    CAUSE

    This issue was caused by a change in the format used by Microsoft Windows to provide the file and folder list to CuteFTP. CuteFTP does not recognize the new format and fails to parse the listing correctly.

    Viewing all 785 articles
    Browse latest View live