Project

General

Profile

Actions

Bug #11234

closed

Installation Issue

Added by Jeff Widgren 8 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/10/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
New Chirp Install
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

I downloaded the latest Chirp for Windows, today. I launched the installation like always. I do not accept the defaults, instead I set a custom install path with the following naming scheme. C:\Program Files (x86)\CHIRP-next-2024-03-10

What changed tonight was... While I deleted the default CHIRP install folder, therefore what was left in the install path was C:\Program Files (x86)\ I accidentally pressed the ENTER key on my keyboard. But, instead of installing CHIRP into Program Files (x86) it started deleting all the existing files and folders as part of its install process. As quickly as I noticed this I cancelled the install via the Task Manager. And then proceeded to purchase a File Recovery Utility to recover 1,000's of missing files.

I realize that I triggered the installation, but I would have never imagined that the installation would start deleting in mass.

Is this by design or oversite?

Actions

Also available in: Atom PDF