Scan2Deploy 2.0 probleme profile

I loose all my profile.
After Launch Scan2Deploy 2.0 can’t create profile and select model/SKU/Os version…
I import my .TAR et dont want import too…
I tryed unistall reinstall, nothing change
I tryed do delete file in roamming, its work one time but cant see my lan files to export or import…
After reboot unistall/install nothing work.
I try an other computer, i can import my file

when i try import :


Hello @jessy_humbert

After deleting the files under roaming folder and uninstalling, unfortunately it is not possible to automatically recover your profiles anymore.
If you have a backup of your profiles you can import them on the new instance, but all the Wi-Fi credentials will be lost, and you need to re-enter them again.
This is not a misbehavior, but a a security system designed to prevent that a malicious user can gather information to violate the Wi-Fi networks you set up into the profiles.

As for the misbehavior found, it is difficult to say what the exact cause is.
Scan2Deploy Studio is a client-server app based on a client GUI and a local server back-end that manages business logic and profile data. A possible reason could be a communication delay between the client and server part of the app. This could happen for example due to a slow DNS resolution state.
On one occasion it happened to me too, by playing with Scan2Deploy Studio while I was activating two concurrent connections to Ethernet and a different WiFi network at the same time. The PC’s network configuration took a while to stabilize, and by maneuvering on Scan2deploy it broke down.
But all I had to do was close Scan2Deploy (I used the ‘Exit’ command from the try Icon, which stops also the server), restart Scan2Deploy Studio, wait a few moments and all the configuration was restored correctly without the need to uninstall.

In any case we’ll track the issue.

If the following folders are still present on your workstation:

C:\Users\<YourName>\AppData\Roaming\Scan2Deploy Studio\logs

You can open a support ticket at Datalogic Technical Support and send the logs you can find in those folders for further analysis. We investigate them looking for possible solutions or at least to dig the root causes of the issue, if possible.

Simone Callegari
Mobile Products L3 Specialist - SW Engineer | Datalogic

he reason for this behavior is Windows and Scan2Deploy manufacturers. Windows reserves ports from 49152 for Hyper-V:

C:\Windows\System32>netsh int ipv4 show dynamicport tcp
Protocol tcp Dynamic Port Range

Start Port : 49152
Number of Ports : 16384

The Scan2Deploy manufacturer just uses ports for java.exe TCP 51070 and Scan2Deploy Studio TCP 51010.

java -jar “C:\Program Files (x86)\Datalogic\Scan2Deploy Studio\resources\app.asar.unpacked\generator-server.jar” 51070
“C:\Program Files (x86)\Datalogic\Scan2Deploy Studio\Scan2Deploy Studio.exe” “C:\Program Files (x86)\Datalogic\Scan2Deploy Studio\resources\app.asar\src\server\dist\server.js”

Ports 51070 and 51010 are reserved for Windows

C:\Windows\System32>netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port

  5357        5357
 49778       49877
 49878       49977
 50000       50059     *
 50060       50159
 50160       50259
 50260       50359
 50360       50459
 50460       50559
 50560       50659
 50660       50759
 50760       50859
 50913       51012
 51070       51070     *
 51071       51170
 51171       51270
 51271       51370
 51371       51470
 52015       52114
 60723       60822
 60823       60922
 60923       61022
 61023       61122
 61123       61222
 61223       61322
 61323       61422
 61423       61522
 61523       61622
 61623       61722
 61723       61822
 61823       61922
 61923       62022
 62023       62122
 62123       62222
 62223       62322
    • Administered port exclusions.

To unlock the ports you need to run the following commands.

net stop winnat
netsh int ipv4 add excludedportrange protocol=tcp startport=51070 numberofports=1
netsh int ipv4 add excludedportrange protocol=tcp startport=51010 numberofports=1
net stop winnat

C:\Windows\System32>netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port

  5357        5357
 50000       50059     *
 51010       51010     *
 51070       51070     *
    • Administered port exclusions.

Ideally, the manufacturer should change the listening ports of these two services to other ports not reserved by Windows.

Hello @Marcin_Sempek,

The dynamic port range is not reserved in its entirety for Hypervisor.
The range is dynamically assigned as needed.

Here is a little bit more information about the Dynamic Port Range:

There was a defect in a Windows Update that caused Hypervisor to reserve too many ports.
Systems that have not updated may run into issues with many applications due to this defect.

The solution you proposed would be a good work around for this defect.
Additionally, a fresh install of Windows should not have this issue.

For more information regarding this defect you can read here:

We are investigating a solution for Scan2Deploy Studio that would account for this behavior.

Drew Hugentobler
L3 Mobile Computer Specialist Support Engineer

1 Like