perl -e "for (qx[wmic process get processid,parentprocessid,executable
+path ]){next unless m/perl.+\Q$$\E/;$parent=(split /\s+/,$_) [1] ;qx|
+taskkill /PID $parent|} "
[download]

why not just Win32::Getppid (oops thanks soonix!)?

use Win32::Getppid;
 
my $parent_pid = getppid;
[download]

bw, bliako

edit: primitive os, brutal practices :)

@bliako: Thanks this worked to get the process ID!

@NetWallah: yes and it does work as expected.

I see no differences in win7 win10 behaviour for the following simple script (removing sounds and other amenities)

use strict;
use warnings;

$|++; #autoflush output

quit();

sub quit {
    my $sleep = 3;
    while ( $sleep ){
        print "\rQuitting in $sleep sec.";
        sleep 1;
        $sleep--;
    }
    exit;
}
[download]

I find no differences even if the .pl program is doubleclicked AND .pl files are associated with a valid perl.exe interpreter. Is this your use case? Because normally a command prompt previously started is persistent. Anyway in both circumstances and in both OSs I see no different behaviour.

You can be interested in a more complex solution as you can read in Handling MSWin Script Output, where I posted the following code:

use strict;
use Win32::Process::Info;

my $pihandle = Win32::Process::Info->new();
my @procinfo = $pihandle->GetProcInfo();

my $ParentPID;
my %ProcNames;

foreach my $PIDInfo (@procinfo) {
    $ProcNames{$PIDInfo->{ProcessId}} = $PIDInfo->{Name};

    if ($PIDInfo->{ProcessId} == $$) {
        $ParentPID = $PIDInfo->{ParentProcessId};
        last;
    }
}

print "Parent's name is [", $ProcNames{$ParentPID}, "]\n";


if ( $ProcNames{$ParentPID} eq 'OpenWith.exe' or $ProcNames{$ParentPID
+} eq 'explorer.exe') {
    print 'Press ENTER to close the window: ';
    <>;
}
else{ print "..exiting normally\n"; }
[download]

L*

Actually exit exits perl program and returns value, it doesn't close terminals. It looks as if you opened cmd then ran perl program which will kill cmd. You can run program using perl interpreter directly which will close terminal immediately after finishing script. You can also add something like this but this will kill all command prompts.

 
system("taskkill /im cmd.exe /f");
[download]

This is at best unwise, this will silently forcibly kill all instances of cmd.exe, you have no idea what the user may be doing on their system.

This was tested and does not work under Windows 10.