Logitech MX Master 3 losing connectivity

I'm starting to panic I see no other partitions on the USB stick.

Don’t panic — this is fixable. You created the tarball in Slax and the Slax listing showed it on the stick, so it almost certainly exists. Windows just might be showing the stick differently (drive letter, hidden partition, filename characters, etc.. Let’s look for it methodically.
Follow these steps in Windows (copy/paste the PowerShell blocks I give). Run them one at a time and paste the output if anything looks unfamiliar.
1) Confirm the USB drive(s) Windows sees
Open PowerShell (just type PowerShell in Start and run it) and paste:
Get-WmiObject Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize

• DriveType 2 = removable USB, 3 = local fixed, 5 = CDROM. Note the DeviceID(s) for removable drives (e.g. E.

2) Quick Explorer-style search (fast)
If you saw a drive letter (say E, open File Explorer → click the drive, and in the search box type:
mouselinuxlogs*.tgz
(That will find files with that prefix even if some characters differ.
3) PowerShell: search removable/fixed drives for the tarball
This searches all available drives that Windows can access:
$drives = (Get-WmiObject Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path "$d*" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue |
Select-Object @{Name='Drive';Expression={$d}}, FullName, Length, LastWriteTime
}
If it finds the file the FullName will tell you exactly where it is.
4) If a match is found — copy it to Desktop so attaching is easy
(Replace <FullName> with the path returned)
Copy-Item -Path '<FullName>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
5) If search above returns nothing, try a looser search for any recent .tgz
$drives = (Get-WmiObject Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Looking for .tgz on $d ..."
Get-ChildItem -Path "$d*" -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 20
}
That will list the most recent .tgz files if the name was changed or mangled.
6) If you still see nothing

• Tell me the DeviceID(s) shown by step (1).
• Check Disk Management (press Win+R, type diskmgmt.msc) and tell me whether the removable stick shows multiple partitions (some sticks show a hidden EFI or installer partition that Explorer may not show the data partition).
• Tell me whether you ejected the stick in Slax before removing (if not, a write might not have completed). If you didn’t unmount/eject in Slax, the copy might not have flushed — but you ran cp and then saw the ls showing the file, so it likely copied.

If you want one single copy/paste block that searches all drives and copies any matching tarballs to your Desktop automatically, run this (in PowerShell):
$drives = (Get-WmiObject Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Get-ChildItem -Path "$d*" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue |
ForEach-Object {
$src = $.FullName
$dest = Join-Path $env:USERPROFILE\Desktop $.Name
Copy-Item -Path $src -Destination $dest -Force
Write-Host "Copied $src -> $dest"
}
}
Run that and paste the output here.
If any step reports an error or you’re unsure what the drive letter is, paste the exact PowerShell output you got and I’ll tell you the next command to run. I’ll stay with you until we find the tarball (or we’ll extract the necessary snippets another way).

The last 3 commands I executed in Slax:

sync
unmount /media/$(ls /media | head -n1)
reboot

PS C:\WINDOWS\system32> Get-WmiObject Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
At line:1 char:134
+ ... eName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1 ...
+ ~
Missing ')' in method call.
At line:1 char:134
+ ... eSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @ ...
+ ~~~~~~~~~~
Unexpected token '$.Size/1GB' in expression or statement.
At line:1 char:144
+ ... System, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{ ...
+ ~
Missing argument in parameter list.
At line:1 char:119
+ ... iveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]:: ...
+ ~
Missing closing '}' in statement block or type definition.
At line:1 char:146
+ ... ystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{N ...
+ ~
The hash literal was incomplete.
At line:1 char:146
+ ... stem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Na ...
+ ~
Unexpected token ')' in expression or statement.
At line:1 char:147
+ ... tem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Nam ...
+ ~
Unexpected token '}' in expression or statement.
At line:1 char:148
+ ... em, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name ...
+ ~
Unexpected token '}' in expression or statement.
At line:1 char:215
+ ... me='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
+ ~~~~~~~~~
Unexpected token '-AutoSize' in expression or statement.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingEndParenthesisInMethodCall

PS C:\WINDOWS\system32>

You did the right Slax steps and the tarball was created & copied to the USB in Slax — Slax’s listing showed mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz on the stick.
Don’t panic — Windows sometimes hides or treats files with unusual characters differently. Let’s find it quickly from Windows. Please run the short PowerShell checks below (copy/paste each block into an elevated PowerShell window) and paste the output back here if anything looks odd.
1) Show all drives Windows sees (so we know the USB drive letter)
Get-WmiObject Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
Look for DriveType 2 (removable) or 3 (local). Note the DeviceID(s) like E:.
2) Quick Explorer search (if you prefer GUI)

• Open File Explorer, click the USB drive, type this into the search box (top-right) and press Enter:
  mouselinuxlogs*.tgz
• Also enable View → Options → View → Show hidden files, folders and drives.

If that finds it, copy it to your Desktop and attach it.
3) PowerShell: search every accessible drive for the tarball and copy it to your Desktop (automatic)
Copy/paste and run this entire block in PowerShell — it will search removable/local drives, report any matches, and copy any found file(s) to your Desktop:
$drives = (Get-WmiObject Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Searching $d ..." -ForegroundColor Cyan
Get-ChildItem -Path "$d*" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue |
ForEach-Object {
$src = $.FullName
$dest = Join-Path $env:USERPROFILE\Desktop $.Name
Copy-Item -Path $src -Destination $dest -Force
Write-Host "Copied $src -> $dest" -ForegroundColor Green
}
}
If it prints "Copied ..." — the file is now on your Desktop (attach it from there). Paste the output here if you want me to confirm.
4) If the previous search finds nothing, try a looser search for any recent .tgz on the stick
$drives = (Get-WmiObject Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Looking for .tgz on $d ..." -ForegroundColor Cyan
Get-ChildItem -Path "$d*" -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending |
Select-Object FullName, Length, LastWriteTime -First 20
}
Paste the output here — I’ll spot the tarball or anything that looks like it.
5) If still nothing — quick checks

• Make sure the same physical USB stick is inserted (sometimes multiple sticks are present).
• Try a different USB port (rear-port preferred).
• Open Disk Management (Win+R → diskmgmt.msc) and check the removable disk — let me know if you see a small partition without a drive letter (some sticks have multiple partitions).
• If you can’t find it in Windows, we can boot the machine back to Slax (or another Linux live USB) and re-copy the tarball with a simpler filename (no colons or plus signs), e.g.:
  cp /tmp/mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz /media/<mount>/mouselinuxlogs_2025-10-22T025516.tgz

Why this can happen

• Filenames with characters like ":" or "+" are allowed/visible on Linux but problematic in Windows Explorer; Windows may show altered names or the file may not be easy to spot with the exact name. The PowerShell wildcard search will find it regardless of character differences. The Slax ls output confirmed the tarball existed on the stick.

Run the PowerShell copy block in step 3 and paste the output here. I’ll guide the next step immediately and — if needed — walk you through re-copying it from Slax with a safe filename.

You’re okay — don’t panic. The Slax output earlier shows the tarball was created and copied to the USB (mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz), so the file almost certainly exists on the stick.
Your PowerShell error came from a small syntax issue in the command you pasted (you used $. instead of $_. and the hash expression wasn’t closed). I’ll give you corrected, safe commands to run in Windows PowerShell that will (1) show the drives Windows sees, (2) search the removable drive(s) for the tarball, and (3) copy any match to your Desktop so you can attach it to the forum.
Step A — list the drives Windows sees (safe)
Open PowerShell (no admin required) and paste this:
Get-CimInstance -ClassName Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize

• DriveType 2 = removable (USB), 3 = fixed (internal). Note the DeviceID(s) you see (for example E.

Step B — search for the tarball and copy any match to your Desktop (one block)
Copy and paste this whole block into PowerShell (it searches removable & fixed drives Windows can access, finds any file named like mouselinuxlogs*.tgz, and copies matches to your Desktop):
$drives = (Get-CimInstance -ClassName Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path "$d*" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue |
ForEach-Object {
$src = $.FullName
$dest = Join-Path $env:USERPROFILE\Desktop $.Name
Copy-Item -Path $src -Destination $dest -Force
Write-Host "Copied: $src"
}
}
If nothing is found, run the looser search below (searches for any recent .tgz on the same drives):
$drives = (Get-CimInstance -ClassName Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Looking for .tgz on $d ..."
Get-ChildItem -Path "$d*" -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
}
Step C — check the Desktop and attach

• After the copy command runs, check your Desktop for the tarball. Attach that Desktop copy using the forum Attach Files (paperclip) button.
• If the command printed “Copied: …” you can paste that path here so I can confirm.

If the search still finds nothing

• Tell me the DeviceID(s) from Step A (paste the output). I’ll give a command that searches all partitions and also show a Disk Management check to confirm the stick’s partitions.
• Also confirm whether you ejected the USB in Slax before removing it. If you removed the stick without unmounting, writes could be incomplete — but your earlier Slax ls output showed the file on the stick, so that’s unlikely.

If you prefer I can give one single copy/paste block that:

• lists logical disks (again),
• searches only the likely removable drive letter you saw earlier,
• and copies any found file to Desktop — tell me the drive letter (e.g. E and I’ll give that one-liner.

Run the commands above and paste the PowerShell output (or the “Copied:” lines) here. I’ll guide the attach step and then parse the logs as soon as the tarball is attached.

PS C:\WINDOWS\system32> Get-CimInstance -ClassName Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
At line:1 char:147
+ ... eName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1 ...
+ ~
Missing ')' in method call.
At line:1 char:147
+ ... eSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @ ...
+ ~~~~~~~~~~
Unexpected token '$.Size/1GB' in expression or statement.
At line:1 char:157
+ ... System, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{ ...
+ ~
Missing argument in parameter list.
At line:1 char:132
+ ... iveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]:: ...
+ ~
Missing closing '}' in statement block or type definition.
At line:1 char:159
+ ... ystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{N ...
+ ~
The hash literal was incomplete.
At line:1 char:159
+ ... stem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Na ...
+ ~
Unexpected token ')' in expression or statement.
At line:1 char:160
+ ... tem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Nam ...
+ ~
Unexpected token '}' in expression or statement.
At line:1 char:161
+ ... em, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name ...
+ ~
Unexpected token '}' in expression or statement.
At line:1 char:228
+ ... me='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
+ ~~~~~~~~~
Unexpected token '-AutoSize' in expression or statement.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingEndParenthesisInMethodCall

PS C:\WINDOWS\system32>

You’re fine — the tarball was created in Slax and Slax showed it on the stick (mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz). I can see that in your Slax listing.
Your PowerShell error is just a small syntax problem (you used $. instead of $_). Don’t worry — run the exact commands below. I’ll walk you through finding and copying the tarball to your Desktop so you can attach it to the forum.
Step 1 — list Windows drives (safe, simple)
Copy‑paste this into PowerShell (exactly as shown):
Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize
Note the drive letter(s) for removable media (e.g. E. If you see the USB drive letter, use that in Step 2. If you prefer the Win32 view, this corrected command also works:
Get-CimInstance -ClassName Win32LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize
Important: copy/paste that second line exactly — it uses $_ (underscore) not $.
Step 2 — search the stick and copy any matching tarball to Desktop
Copy‑paste this whole block (it searches all accessible fixed & removable drives, finds files named like the tarball, and copies matches to your Desktop):
$drives = (Get-CimInstance -ClassName Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path "$d*" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue |
ForEach-Object {
$src = $.FullName
$dest = Join-Path $env:USERPROFILE\Desktop $.Name
Copy-Item -Path $src -Destination $dest -Force
Write-Host "Copied: $src -> $dest"
}
}

• If it finds and copies the file you’ll see “Copied: …” lines. After that the tarball will be on your Desktop ready to attach.

Step 3 — if nothing is found, run a looser search
If the strict search returns nothing, run this to list recent .tgz files on the same drives:
$drives = (Get-CimInstance -ClassName Win32LogicalDisk | Where-Object { $.DriveType -in 2,3 }).DeviceID
foreach ($d in $drives) {
Write-Host "Looking for .tgz on $d ..."
Get-ChildItem -Path "$d*" -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
}
Post the output (or the “Copied:” line) here and I’ll confirm the exact file path to attach. If PowerShell reports any errors, paste those messages and I’ll guide the fix.
Quick notes/possible reasons you couldn’t see it in Explorer

• The filename contains colons and a plus sign (timestamp); Explorer sometimes hides or treats characters oddly — PowerShell search will still find it.
• If you removed the stick from the PC without ejecting in Slax, a copy could be incomplete — but your Slax ls showed the file on the stick, so it should be present.

If you’d like, I can give a single one‑liner that searches just a specific drive letter (e.g. E and copies a match to Desktop — tell me the drive letter you see from Step 1 and I’ll post that exact command.
Run Step 1 then Step 2 and paste whatever output you get (especially any “Copied:” lines). I’ll stay here and guide you the rest of the way.

PS C:\WINDOWS\system32> Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize

Name Root Used Free
---- ---- ---- ----
C C:\ 604262703104 395122495488
D D:\ 3142088114176 1858857086976
E E:\ 1235968 2911232
F F:\ 3104407552 58871185408


PS C:\WINDOWS\system32>

You’re OK — don’t panic. Slax showed the tarball was created and copied to the USB (mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz), so it almost certainly exists on the stick.
Let’s find and copy it to your Windows Desktop so you can attach it. Copy/paste these PowerShell commands (one at a time) and tell me the output.
1) Confirm drive letters quickly (you already posted this — E: and F: are present). If you want to re‑check:
Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize
2) Search the likely USB drive(s) and show any matching filename (replace E: and F: only if your USB is on a different letter):
Get-ChildItem -Path 'E:\' -Filter 'mouselinuxlogs.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
Get-ChildItem -Path 'F:\' -Filter 'mouselinuxlogs.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime

• If either command returns a path, paste that FullName here and run the Copy command in step 3.

3) If you find a match, copy it to your Desktop (replace <FullName> with the path returned):
Copy-Item -Path '<FullName>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
4) If the exact name search returns nothing, search for any .tgz files (recent / small ones) on those drives — this will catch a name that Windows altered:
Get-ChildItem -Path 'E:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
Get-ChildItem -Path 'F:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30

• Look for a file roughly 2.3 MB in size (your Slax tarball was ~2,374,332 bytes). If you see a likely match, copy it to Desktop with the Copy-Item command above.

5) If nothing is found

• Tell me the output of Get-PSDrive (you already ran it — you can paste it again).
• Also check Disk Management (Win+R → diskmgmt.msc) and tell me whether the removable disk shows a partition without a drive letter (some USB sticks have multiple partitions).
• If Windows still can’t see it, we’ll reboot to Slax (or another Linux live USB) and re-copy the tarball with a safe filename (no colons/plus signs) — e.g. mouselinuxlogs_20251022_025516.tgz — then repeat the attach from Windows. That’s trivial and will guarantee a Windows‑friendly filename.

Run the search commands now and paste whatever output you get (or the “Copied to Desktop” message). I’ll guide the attach step next and then parse the logs as soon as you attach the tarball.

PS C:\WINDOWS\system32> Get-CimInstance -ClassName Win32_LogicalDisk | Format-Table DeviceID, DriveType, VolumeName, FileSystem, @{Name='SizeGB';Expression={[math]::Round($_.Size/1GB,2)}}, @{Name='FreeGB';Expression={[math]::Round($_.FreeSpace/1GB,2)}} -AutoSize

DeviceID DriveType VolumeName FileSystem SizeGB FreeGB
-------- --------- ---------- ---------- ------ ------
C: 3 Windows 10 Professional NTFS 930.75 367.98
D: 3 Backup NTFS 4657.49 1731.2
E: 2 DYMO FAT 0 0
F: 2 UUI FAT32 57.72 54.83


PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize

Name Root Used Free
---- ---- ---- ----
C C:\ 604265476096 395119722496
D D:\ 3142088114176 1858857086976
E E:\ 1235968 2911232
F F:\ 3104407552 58871185408

Good — thanks, that confirms Windows sees the stick (E: and F. F: (UUI) is the likely place the tarball landed. Don’t worry — the Slax session showed the tarball was written to the stick, so it should be findable on Windows.
Please run these two short PowerShell commands (copy/paste each line) and paste the output here if anything returns nothing or an error.
1) Look for the exact tarball name on F: (fast — likely hit)
Get-ChildItem -Path 'F:\' -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
2) If that finds nothing, list recent .tgz files on F: (catches a renamed/altered name)
Get-ChildItem -Path 'F:\' -Include *.tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
If either command prints a FullName (path), run this to copy it to your Desktop (replace <FullName> with the path printed):
Copy-Item -Path '<FullName>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
Quick GUI alternative: open File Explorer → click F: → in the top-right search box type:
mouselinuxlogs*.tgz
and press Enter. If you see it, copy → Desktop and attach from your Desktop.
If you still find nothing

• Tell me the outputs of the two PowerShell commands above (paste them here).
• If power output shows no matches but you remember the Slax ls output (it did show mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz), we can either:
  • Reboot back to Slax (or boot another Linux live USB) and re‑copy the tarball with a Windows‑safe name (for example run in Slax: cp /media/<usb>/mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz /media/<usb>/mouselinuxlogs_20251022_025516.tgz), or
  • Check Disk Management (Win+R → diskmgmt.msc) to confirm the stick’s partitions/letters if Windows is mounting an unexpected partition.

If you want I can give one PowerShell block that searches E: and F: and copies any match to Desktop automatically — say “run auto‑copy” and I’ll post that one‑liner.
Once you’ve copied the file to Desktop, attach it to the forum (paperclip / Attach files). As soon as it’s attached I’ll download and parse the logs and tell you the single next action.

You’re fine — don’t panic. Slax’s earlier ls showed the tarball was copied to the stick (mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz), and your Windows drives list shows two removable-ish volumes (E: and F. The tarball size from Slax (~2.37 MB) matches the free/used numbers for E:, so it’s very likely on E:.
Do this now — exact PowerShell commands to find & copy the tarball to your Desktop (copy/paste each line)
1) Quick check (show drives you already ran — just to confirm):
Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize
2) Search E: (likely) for the tarball:
Get-ChildItem -Path 'E:\' -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
If that prints a path, copy it to Desktop:
Copy-Item -Path 'E:\<the-file-name-found>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
3) If step 2 returns nothing, search F: as well:
Get-ChildItem -Path 'F:\' -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
4) If neither exact-name search finds it, run a looser search for any .tgz (shows the most recent 30):
Get-ChildItem -Path 'E:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
Get-ChildItem -Path 'F:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
If you see a file about 2.3 MB (≈ 2,374,332 bytes) that looks like it, copy that FullName to Desktop with the Copy-Item command above.
One automatic block (search both drives and copy matches to Desktop)
If you want a single paste that searches both drives and copies any matching mouselinuxlogs.tgz to Desktop, run this:
$drives = @('E:\','F:\')
foreach ($d in $drives) { Write-Host "Searching $d ..." ; Get-ChildItem -Path "$d" -Filter 'mouselinuxlogs*.tgz' -Recurse -Force -ErrorAction SilentlyContinue | ForEach-Object { $src=$.FullName; $dest=Join-Path $env:USERPROFILE\Desktop $.Name; Copy-Item -Path $src -Destination $dest -Force; Write-Host "Copied: $src -> $dest" } }
What to do after copy

• Check your Desktop for the .tgz and attach it using the forum “Attach files” / paperclip.
• If the commands print a path but the copy fails, paste the printed path here and I’ll give the exact Copy-Item command.

If nothing is found

• Tell me the output from the exact search commands above (paste it here).
• Also confirm whether you ejected the USB in Slax before removing it (you showed you ran sync/unmount earlier so that’s fine). If Windows still can’t see it, we can boot Slax again and re-copy the tarball using a Windows‑safe filename (no colons or plus signs), e.g. mouselinuxlogs_20251022_025516.tgz, then try the attach step again. That’s quick and guaranteed to work.

If you run any of the commands above, paste the output here — I’ll guide the final copy/attach step immediately.

PS C:\WINDOWS\system32> Get-PSDrive -PSProvider FileSystem | Format-Table Name, Root, Used, Free -AutoSize

Name Root Used Free
---- ---- ---- ----
C C:\ 604265476096 395119722496
D D:\ 3142088114176 1858857086976
E E:\ 1235968 2911232
F F:\ 3104407552 58871185408


PS C:\WINDOWS\system32> Get-ChildItem -Path 'E:\' -Filter 'mouselinuxlogs.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
PS C:\WINDOWS\system32> Get-ChildItem -Path 'F:\' -Filter 'mouselinuxlogs.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
PS C:\WINDOWS\system32> Get-ChildItem -Path 'E:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
PS C:\WINDOWS\system32> Get-ChildItem -Path 'F:\' -Include .tgz -Recurse -Force -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object FullName, Length, LastWriteTime -First 30
PS C:\WINDOWS\system32>

You’re doing fine — breathe. The Slax session showed the tarball was created and copied to the stick (mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz), so it very likely exists on the USB. I can help you find it from Windows — let’s try a few reliable PowerShell searches and, if we find it, copy it to your Desktop so you can attach it to the forum. I’ll explain each step so nothing unexpected happens.
Why this can be tricky

• Filenames created on Linux can include characters (":" and "+") that confuse Explorer searches or look different in Windows. The Slax listing showed the tarball on the stick earlier.

Step 1 — quick root listing (shows top-level files on each USB volume)
Run these two commands (copy/paste each line) so I can see what’s at the root of the two removable drives Windows shows (E: and F: from your output):
Get-ChildItem -Path 'E:\' -Force | Select-Object Name, Length, LastWriteTime
Get-ChildItem -Path 'F:\' -Force | Select-Object Name, Length, LastWriteTime
Paste the output here if anything looks unfamiliar (I’ll interpret it). If you see a file name similar to mouselinuxlogs or any .tgz, tell me which one.
Step 2 — robust wildcard search across the two drives (this finds files even if the name includes unusual characters)
Copy and paste this block exactly into PowerShell and run it:
$drives = @('E:\','F:\')
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path $d -Recurse -Force -ErrorAction SilentlyContinue |
Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' -or $_.Extension -eq '.tgz' } |
Select-Object FullName, Name, Length, LastWriteTime
}
This will list any file whose name contains “mouselinuxlogs” or “mouse” or any .tgz file on either E: or F:.
Step 3 — if a match appears, copy it to Desktop
If the previous command prints one or more paths, copy one of the found files to your Desktop by running (replace <FullName> with the FullName printed):
Copy-Item -Path '<FullName>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
Then check your Desktop and attach that copied file to the forum.
One automatic block (search + copy any matches to Desktop) — safe to run if you want a single command:
If you prefer one command that both searches and copies any matches to Desktop, run this:
$drives = @('E:\','F:\')
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path $d -Recurse -Force -ErrorAction SilentlyContinue |
Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' -or $.Extension -eq '.tgz' } |
ForEach-Object { Copy-Item -Path $.FullName -Destination $env:USERPROFILE\Desktop -Force; Write-Host "Copied: $($_.FullName) -> Desktop" }
}
If that prints “Copied: …” you’re done — attach the Desktop copy.
If these searches find nothing

• Tell me the exact output from Step 1 and Step 2 and I’ll interpret it.
• Also run Disk Management (Win+R → diskmgmt.msc) and tell me whether the removable disk shows multiple partitions (sometimes a small boot/EFI partition is visible as one drive letter and the larger data partition has a different letter or no letter). If the stick has an unusual partition layout we’ll either assign a letter or re‑boot to Slax and re‑copy the tarball using a Windows‑safe name (e.g. mouselinuxlogs_20251022_025516.tgz). Re-copying from Slax with a safe name is quick and guaranteed to work if Windows is still being awkward.

If you want me to paste a single command that does everything (search both drives, list matches and copy them) — say “run auto‑copy” and I’ll give that single pasteable block again.
Run Step 1 and Step 2 now and paste the outputs (or the “Copied: …” lines if you used the auto‑copy). I’ll guide you the rest of the way and stay with you until the file is attached.

PS C:\WINDOWS\system32> Get-ChildItem -Path 'E:\' -Force | Select-Object Name, Length, LastWriteTime

Name Length LastWriteTime
---- ------ -------------
System Volume Information 14/12/2023 00:09:06
DYMOLabelLightv2.exe 1231304 30/11/2023 16:28:36
.dropbox.device 56 14/12/2023 21:11:10


PS C:\WINDOWS\system32> Get-ChildItem -Path 'F:\' -Force | Select-Object Name, Length, LastWriteTime

Name Length LastWriteTime
---- ------ -------------
System Volume Information 26/07/2023 05:00:16
uui 26/07/2023 05:00:18
slax 21/01/2023 10:58:44
readme.txt 823 20/01/2023 22:38:24
Uni-USB-Installer-Copying.txt 49418 30/01/2022 11:22:08
Uni-USB-Installer-Readme.txt 2691 30/01/2022 11:21:44
license.txt 18092 18/03/2021 14:13:08


PS C:\WINDOWS\system32>

Good — thanks for the E: / F: listings. Don’t worry, the Slax run did create the tarball on the stick (I can see Slax’s ls output showing mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz).
Why Windows can’t find it (brief)

• Linux filenames can include characters Windows treats oddly (colons :, plus +, etc.. That can make Explorer searches or simple filters miss the file even though it’s on the stick.
• Some USB keys have multiple partitions (boot/EFI + data) and Windows shows a different partition letter than Slax did. If that’s the case the file is on the other partition that Windows isn’t showing.

Next step — one safe PowerShell block to find & copy the tarball
Run this exact block in PowerShell (paste the whole block). It searches E: and F: for anything with “mouse” in the name or any .tgz, and if it finds a match it copies it to your Desktop so you can attach it here:
$drives = @('E:\','F:\')
foreach ($d in $drives) {
Write-Host "Searching $d ..."
Get-ChildItem -Path $d -Recurse -Force -ErrorAction SilentlyContinue |
Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' -or $.Extension -eq '.tgz' } |
ForEach-Object {
$src = $.FullName
$dest = Join-Path $env:USERPROFILE\Desktop $_.Name
Copy-Item -Path $src -Destination $dest -Force
Write-Host "Copied: $src -> $dest"
}
}

• If you get any “Copied: …” lines, check your Desktop and attach the copied .tgz here.
• If the command prints nothing, paste the output here (I’ll interpret).

If that still finds nothing
1) Check Disk Management (Win+R → diskmgmt.msc) and tell me whether the removable disk shows more than one partition or any partition without a drive letter — paste a screenshot or the text. If Slax wrote to a different partition, Windows might be mounting the boot/installer partition (folders like slax, uui) while the data partition (where the tarball is) isn’t visible.
2) If Disk Management looks normal and the PowerShell search still shows nothing, we can:

• Boot back to Slax briefly and re-copy the tarball with a Windows‑safe name (no colons or plus signs). Example Slax command (run as root):
  cp /media/$(ls /media | head -n1)/mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz /media/$(ls /media | head -n1)/mouselinuxlogs_20251022_025516.tgz
• Then re-insert the stick into Windows and attach mouselinuxlogs_20251022_025516.tgz.

Finally — one reassurance

• Slax showed the file existed on the stick earlier, so we’re not starting from zero; we just need to locate it from Windows (filename/partition quirk).

Run the PowerShell block above and paste any output here (or say “no output” and I’ll walk you through Disk Management). I’ll stay with you until we have the tarball on your Desktop ready to attach.

PS C:\WINDOWS\system32> $drives = @('E:\','F:\')
PS C:\WINDOWS\system32> foreach ($d in $drives) {
>> Write-Host "Searching $d ..."
>> Get-ChildItem -Path $d -Recurse -Force -ErrorAction SilentlyContinue |
>> Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' -or $_.Extension -eq '.tgz' } |
>> Select-Object FullName, Name, Length, LastWriteTime
>> }
Searching E:\ ...
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Searching F:\ ...
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:4 char:16
+ Where-Object { $.Name -like 'mouselinuxlogs' -or $.Name -like 'mouse' ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32>

Good — thanks for the E: and F: listings. Don’t worry — the tarball was shown on the stick when you ran ls in Slax, so it very likely exists (Slax showed mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz on the USB).
Two safe paths to finish this quickly. Pick whichever you prefer:
Option A — keep working in Windows (I’ll give exact, corrected PowerShell commands)

• Run these exact commands (copy/paste each block). They fix the earlier syntax issues and will find the file even if Windows altered the name.

1) Search for any .tgz files on E: and F: (safe, fast):
Get-ChildItem -Path 'E:*','F:*' -Include '*.tgz' -Recurse -Force -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
2) If you want to search by filename fragments (covers odd characters or mangled names):
Get-ChildItem -Path 'E:*','F:*' -Recurse -Force -ErrorAction SilentlyContinue | Where-Object { $.Name -match 'mouse' -or $.Name -match 'mouselinux' } | Select-Object FullName, Name, Length, LastWriteTime
3) Or search by approximate size (your tarball was ~2.37 MB):
Get-ChildItem -Path 'E:*','F:*' -Recurse -Force -ErrorAction SilentlyContinue | Where-Object { $.Length -ge 2000000 -and $.Length -le 4000000 } | Select FullName, Name, Length, LastWriteTime
4) If one of the above prints a path that looks like the tarball, copy it to your Desktop (replace <FullName> with the path shown):
Copy-Item -Path '<FullName>' -Destination $env:USERPROFILE\Desktop -Force
Write-Host "Copied to Desktop"
5) Convenience: one command that searches both drives and copies any reasonable match to Desktop:
$paths = 'E:*','F:*'
Get-ChildItem -Path $paths -Recurse -Force -ErrorAction SilentlyContinue |
Where-Object { ($.Extension -eq '.tgz') -and ($.Name -like 'mouselinux' -or ($.Length -ge 2000000 -and $.Length -le 4000000) } |
ForEach-Object { Copy-Item -Path $.FullName -Destination $env:USERPROFILE\Desktop -Force; Write-Host "Copied: $($.FullName) -> Desktop" }
If any “Copied:” line appears, check your Desktop and attach that file to the forum.
Option B — easiest guaranteed fix: boot Slax briefly and re‑copy with a Windows‑safe name

• Because Linux allowed the filename containing colons and a plus sign, Windows may have trouble listing it. The fastest guaranteed way to resolve that is to boot the Slax live USB again and copy the tarball to the stick with a Windows-friendly name (no ":" or "+"), then return to Windows and attach that new file.

If you want me to give the exact Slax one‑liner to run in a Slax terminal (as root) to create a Windows‑safe filename, use this (adjust if your mount point is different):
cp /tmp/mouselinuxlogs_2025-10-22T02:55:16+00:00.tgz /media/$(ls /media | head -n1)/mouselinuxlogs_20251022_025516.tgz && sync && umount /media/$(ls /media | head -n1)

• Then reboot to Windows and attach mouselinuxlogs_20251022_025516.tgz from the USB — it will be visible in Explorer.

If neither option finds the file

• Check Disk Management (Win+R → diskmgmt.msc). If the USB shows multiple partitions and one has no drive letter, tell me what you see and I’ll give the exact steps to assign a drive letter to that partition so Windows can access the data partition. (Some live‑USB sticks expose a small boot partition as one drive letter and the data partition as a second partition without a letter.

Recap / recommendation

• Quickest: run the PowerShell searches above (Option A). If they find/copy the tarball, attach it and I’ll parse the logs immediately.
• If the PowerShell search finds nothing or Disk Management shows an unmounted partition, boot Slax and re-copy with a safe name (Option B) — I can give the exact command and wait while you do it.
• Evidence that the tarball existed on the stick from Slax is recorded here.

Tell me which option you want (A: keep in Windows and run the PowerShell blocks I posted; or B: reboot to Slax and I’ll give the exact copy command). I’ll stay here and guide you step‑by‑step.