OSForensics version 11 android artificact acquisition issue

[xuser]

I followed the tutorial provided on how to acquire android artifacts, everything works until the part where the OSFExtract Apk gets installed to my device then on the PC application I get hit with the following error
"App Install Result: Performing Streamed Install Success
Launching OSFExtract app on android device
OSFExtract app launch successful
Setting up port forwarding
Getting port forwarding status
Failed to get port forwarding status
Socket connection error, invalid socket (18446744073709551615) returned
Stopping port forwarding
Extract finished on Monday, July 27, 2026, 11:22:09
Extract Time Elapsed: 22 Seconds
==================================================
VHD has been unmounted
Error occurred during the acquisition, please review the logs for more information about the error"

How do I fix this?
I'm running OSForensics on Windows 10 x64
I've excluded the software from windows defender firewall but the issue persists

[Chaitanya (PassMark)]

Hi xuser,
We tried to reproduce the issue that you are facing, but even after several different methods we were not able to reproduce the exact same error.

Looking at your log, "Setting up port forwarding" -> "Failed to get port forwarding status." That's the step where OSForensics establishes the connection (over ADB) that lets your phone send its data back to the PC. So this isn't a problem with your app's permissions, it's happening at the ADB layer.

A quick question, is this happening every time, or was it a one-off? Please try the acquisition again a couple of times and let us know whether it fails consistently or only sometimes. This particular step can fail in between if something else on the PC disturbs ADB at the wrong moment, so knowing if it fails consistently or occassionally helps us narrow it down.

The connection uses your PC's local loopback address, so Windows Firewall should ideally not filter that. But, since you have already excluded the application from firewall, we can strike this one out. The most common cause we see for this step failing is another program on the PC that also talks to Android devices over ADB. OSForensics uses a shared ADB background process, and if another app starts, stops, or restarts it mid-acquisition, this exact "port forwarding" step fails. Something like Android Studio or the Android SDK, an emulator, or a phone mirroring/backup app.

So the first thing worth trying, with your phone plugged in:

Close any of the programs above (check the system tray as well).
Open Command Prompt and run:
"C:\Program Files\OSForensics\adb\adb.exe" kill-server
Start the acquisition again.

Let us know if that helps, we'd love to know which one.

If it's still failing after that, the most useful thing you can send us is a log from the phone itself, captured during a failing run. With the device connected, open Command Prompt and run these two lines first (the first line clears the old log), then reproduce the error in OSForensics:

"C:\Program Files\OSForensics\adb\adb.exe" logcat -c
"C:\Program Files\OSForensics\adb\adb.exe" logcat -v time > "%USERPROFILE%\Desktop\osf_phone_log.txt"

Once OSForensics shows the error, close the Command Prompt window and attach the osf_phone_log.txt file from your Desktop to your reply.

Also, can you please confirm if during a failed run, does anything ever appear on the phone's screen (an "Allow" or permission prompt), or does OSForensics fail before the phone shows anything?

With this debug we should be able to get to the bottom of it and assist you further.

Thanks for your patience!