TRIAL AND LICENSE ACTIVATION
Installing does not start the trial. At first application launch, choose to start a 48-hour trial or enter a ten-digit key to activate. Before that choice, no range finder or network diagnostic starts. Trial time includes periods when the program is closed. Trial state is local; starting a trial does not submit an activation request. Windows permission is requested to save the protected machine-wide trial/registration state after an explicit choice. The regular application runs with the current user's normal permissions.
When Activate is selected, the application sends an HTTPS activation request to: https://licensing.aicreatenow.com/api/v1/activate.asp The request contains the entered ten-digit license code, a product-scoped hardware-derived machine identifier, an installation identifier, the Windows computer name and the application version. The receiving server also sees the source public IP and ordinary HTTPS request metadata. Hardware inputs are used locally to derive the identifier; raw hardware identifiers are not submitted as separate activation fields. The server checks the key and machine binding. No Wi-Fi scan results, diagnostic reports, RDP history, passwords or Credential Manager contents are included in the activation request.
After server approval, the app stores a local registration record at <installation folder>\LicenseState\registration.dat. The normal default is C:\Program Files\Wi-Fi Commander\LicenseState\registration.dat. This remembers registered access for the computer without routine license-server checks. It contains a hash of the key, machine/install identity and a local integrity proof protected with Windows machine-scope DPAPI. The raw ten-digit key is not stored in that registration file. The local license record is not a network diagnostic log. Reinstalling after uninstall requires entering the key and contacting the server again. A hardware change may also require a new server-approved activation.
The machine trial record is stored in the 64-bit registry view under HKLM\SOFTWARE\AI Creations Now Software Development\Wi-Fi Commander\Licensing as TrialStateV1. The current user's trial-clock record is under the corresponding HKCU key as TrialClockV1. These small records hold trial/timing/identity state; they are retained after uninstall to avoid starting another trial on reinstall. They contain no network scan results or RDP history. The licensing records are used for application access, not advertising or diagnostic reporting.
PURCHASE LINK AND PAYMENT
The expired-trial screen identifies the purchase provider as Stripe and opens this link in the default browser only when the user clicks it: https://buy.stripe.com/00w9AV1NFbJu0RK4VM5kk0c The displayed offer is a $4.99 lifetime Wi-Fi Commander license. Checkout and any purchase-related customer information are handled by the merchant and Stripe under their own terms and privacy notices. The application does not collect payment-card details or receive them from the browser. The application requires the delivered ten-digit key to activate; clicking the link does not by itself establish registration. Stripe privacy: https://stripe.com/privacy
LOCAL WI-FI RANGE FINDER
After a valid trial or registration, opening the main menu starts nearby Wi-Fi scanning, targeting five seconds between scan starts. The app reads SSIDs, BSSIDs, RSSI, signal quality, band, channel and adapter descriptions. It also reads BSSID relationships using the Windows command "netsh wlan show networks mode=bssid" for Device ID grouping. It does not read Wi-Fi passwords or change saved profiles or connections.
Windows may require Location services and desktop-app location access to expose nearby Wi-Fi details. The app does not bypass permission or change those settings. It does not request GPS coordinates. Driver scans may send ordinary radio probes and temporarily affect Wi-Fi latency. Pause stops repeated scans.
HOME WI-FI MESH ANALYZER: LOCAL DISCOVERY
Choosing Home Wi-Fi Mesh Network Analyzer stops the range finder and first shows the supplied introduction artwork. Clicking Okay starts the local device selector inside the red screen; no mesh worker starts before that action. Closing the introduction returns to the main menu and its range finder. The analyzer reads SSID/BSSID and Windows-reported BSSID/MLO relationships, RSSI, signal quality, frequency, channel, primary adapter identity and connection state. It also reads local IP/default-gateway configuration, interface metrics and gateway MAC data from the Windows neighbor cache to suggest possible device roles and names. Those suggestions do not establish device ownership or physical identity.
Device selection is explicit; the first list has no checked rows. Checked groups and editable friendly names are used to display per-band readings, last-seen times, session signal statistics and strongest-selected-radio information. These selections, names and statistics remain in session memory. The selector targets a scan every 30 seconds and the monitor every ten seconds. Only the primary Wi-Fi interface is actively scanned; a secondary HBS Wi-Fi interface is not independently scanned. The same Windows location-permission requirements as the range finder may apply, without a GPS request.
Ordinary WLAN scanning can send radio probes. If gateway MAC information is missing from the local neighbor cache, discovery may send one ICMP probe to the local gateway before reading that cache again. Mesh mode does not contact public Internet endpoints, perform download/upload benchmarks, capture packets, read Wi-Fi passwords, upload its readings or change network/router settings.
A confirmed change of connection state, primary adapter, connected SSID or AP identity halts scanning, including an AP change caused by roaming. A new baseline requires an explicit restart/reselection. Main Menu or closing the window stops the mesh worker and its owned child processes before changing screens or exiting. Returning to the main menu resumes its nearby Wi-Fi scans.
LIVE BANDWIDTH MONITOR: LOCAL COUNTERS
Choosing Live Bandwidth Monitoring stops the range finder and starts passive observation of one selected physical Wi-Fi or Ethernet adapter. The app reads adapter names/descriptions, connection profile names, interface status, default routes, interface/route metrics, Windows connectivity status and byte counters through .NET and Windows CIM. It samples counters about once per second and refreshes adapter selection about every eight seconds or after a disconnection.
These readings produce live download/upload rates, session maximum rates, downloaded/uploaded/combined totals and elapsed time. They include Internet and local-network traffic on the selected adapter. The feature does not send probes, run a download benchmark, inspect packet contents, identify individual websites or applications, or upload its readings. It does not start a PowerShell process.
Session readings are held only in memory. Reset Totals clears the accumulated values and begins a new session. Main Menu or closing the window stops the monitor and waits for the current read to finish before changing screens or exiting. Returning to the main menu resumes nearby Wi-Fi scanning.
INTERNET HEALTH CHECKER: ACTIVE NETWORK REQUESTS
Choosing Internet Health Checker Benchmark stops the range finder and starts the supplied Internet Monitor diagnostics. Returning with Main Menu stops those diagnostics and their active transfers before restarting Wi-Fi scanning.
The Internet checker reads adapter information, IPv4/default-gateway settings, local/public IP addresses, DNS results, and visible route-hop addresses/names. It tests router/Internet latency, loss, jitter, path MTU, HTTPS/TCP reachability, worldwide route performance and download throughput. These tests generate real network traffic and may use bandwidth or incur charges on a metered connection.
As configured in the supplied script, it contacts:
- Cloudflare: 1.1.1.1 for ping/path tests, www.cloudflare.com/cdn-cgi/trace for public IP, and speed.cloudflare.com for download measurements.
- Google 8.8.8.8 and Quad9 9.9.9.9 for Internet ping targets.
- Your configured DNS resolvers, including a www.microsoft.com lookup and forward/reverse lookups used by the diagnostics.
- ARIN at rdap.arin.net for registration information for the public IP.
- ipwho.is for an approximate public-IP location. The public IP is included in this lookup; returned city/region/country and coordinates are used locally to estimate regional distance. This is IP geolocation, not GPS or precise device location. It is enabled when the Internet checker is opened.
- Public regional endpoints listed in the included script: DigitalOcean Spaces, Amazon regional services, New York institutions/city websites, and Russian websites including Yandex, Sberbank, Moscow State University, VK and Mail.ru. The script tries configured fallback endpoints when necessary.
Remote services and intermediate network operators receive the traffic needed for these requests, including the source public IP, timing and relevant request metadata. Their own policies govern their handling of these requests. Wi-Fi SSID/BSSID lists and full diagnostic reports are not uploaded to these services. No reports are sent to AI Creations Now Software Development.
Health checks target 60-second cycles. The download benchmark requests 104,857,600 bytes (100 MiB) per test. The initial series has four successful tests, spaced by the supplied script's three-minute schedule after successful measurements, followed by a two-hour schedule. Failed attempts may transfer partial data and are retried according to the original script. Actual timing can be later because a diagnostic cycle must finish before the next starts. Pause, Main Menu, or closing the window stops this app's worker and its active child processes. Resume/Restart begins a new session and startup test.
NETWORK AND PORT MONITOR: LOCAL INVENTORY AND PUBLIC TCP CHECK
Choosing Network and Port Monitor stops the range finder, inventories local TCP listeners and UDP endpoints, and automatically requests a public IPv4 TCP reachability report. Run Report repeats these actions on demand. Reports are one-shot; there is no automatic repeating public port check.
The local inventory reads listening/bound addresses and ports, owning process names and IDs, Windows service names, configured Remote Desktop TCP port, active adapter/profile details, local IPv4 configuration and route metrics. These details are used locally to describe endpoints and their possible uses. It does not read process memory, inspect packet contents, stop processes or change firewall, router, adapter or Remote Desktop settings.
The feature sends an HTTPS request to https://portchecker.io/api/me to obtain the source public IPv4, then HTTPS POST requests to https://portchecker.io/api/query containing that public IPv4 and unique local network-facing TCP port numbers, in batches of up to 50. The remote service attempts TCP connections to those public IPv4 ports. Loopback-only listeners are not submitted. UDP endpoints are local inventory only; there is no external UDP or IPv6 test. Process/service names, PIDs, binding addresses, Wi-Fi names and the full local inventory are not included in these API request bodies.
The service receives source public IP, requested port numbers and request metadata. Network operators can observe traffic timing and connection metadata; the API request body is sent over HTTPS. Their policies govern their handling of those requests. A reachable public port may belong to a router or another host behind NAT; it does not prove reachability to this computer. Failed or missing test results remain unknown. The feature sends no report to the publisher and saves no diagnostic history. Main Menu or closing the window stops its worker and owned processes before switching screens or exiting.
LOCAL AREA NETWORK MONITOR: PRIVATE IPV4 DISCOVERY
Choosing Local Area Network Monitor stops the range finder and starts discovery within the displayed private IPv4 scope on one active adapter. The app reads adapter name/description, type, link speed, interface metric, local IPv4/prefix, default gateway and Windows IPv4 neighbor-cache addresses, MACs and states. For a Wi-Fi connection it also reads available SSID, MLD AP BSSID, radio type and signal metadata. It does not read Wi-Fi passwords or capture packet content.
Scan starts target eight seconds; a slow cycle finishes before another begins. The feature sends ICMP probes to private IPv4 hosts in the selected range and combines replies with neighbor-cache evidence. Accepted prefixes are /16 through /30, with at most a /22 host range; subnets broader than /22 are limited to this computer's local /24. The effective scope/limit is displayed. Public IPv4 and IPv6 sweeps are not part of this feature, and no service-port scan is added.
Hostnames are requested through Windows reverse name resolution. Windows may send these requests, including queried private IP addresses, to the computer's configured DNS resolvers. A configured resolver may be outside the local LAN; its handling is governed by its own policies. There is no hardcoded public API, public-IP lookup, download benchmark or publisher reporting in the LAN feature. Normal network/Windows behavior may create neighbor and resolver cache entries.
Device IP, hostname, MAC, latency, status, first/last-seen observations and connection/scope information remain in session memory. Previously observed addresses that are no longer seen are retained for up to thirty minutes after the last observation. A monitored connection/scope change clears the prior LAN history. No inventory export, device-history file or runtime error-log file is created. The unchanged original script in reference\ is for comparison and is not installed or run by this feature.
The app does not alter network settings, router configuration, firewall rules, DNS configuration or device credentials. Main Menu or closing the window stops the private LAN worker and its owned processes before changing screens or exiting. Returning to the yellow screen resumes the Wi-Fi range finder.
INTERNET / NETWORK TOOLS: USER-REQUESTED DIAGNOSTICS
The Internet / Network Tools button stops the range finder and opens a separate menu. Merely viewing that menu does not start a diagnostic. Opening IP Configuration, Netstat or Quick Wi-Fi requests one local snapshot; their action buttons request another. Targeted diagnostics need their action button. RDP shows a confirmation on opening and clears only after Yes. Each tool shows its results in the application. Returning to either menu or closing the screen stops the tool's private worker and owned command processes before continuing. Returning to Main Menu resumes the range finder's nearby Wi-Fi scanning.
DNS Lookup and NSLookup submit the entered name or address through Windows DNS resolution to the configured resolver. DNS Lookup uses DNS-only queries and does not consult the hosts file. PTR converts an IP into its reverse-DNS name. Requested DNS record types and normal query metadata are visible to that resolver. A configured resolver may be on the LAN or a public service. DNS resolution may use existing Windows caches; this tool does not flush them or change system/adapter DNS configuration.
DNS Propagation submits the entered domain to https://api.globalping.io over HTTPS for A/IPv4 lookups from up to thirty geographically distributed probes. It retrieves the currently available probe inventory and selects distinct cities across available continents. Globalping sees your public IP, requested target and normal API metadata. Its probes and their local DNS resolvers receive the domain and DNS query metadata; probe operators and network operators may observe or record their traffic. No AAAA/IPv6 query is requested by this feature. Standard DNS Lookup still supports AAAA when selected.
Globalping measurement requests and results are retrievable by measurement ID and are public. Do not submit internal/private names you do not intend to share with that service. No Globalping login/API key is collected by this version. Service availability, quotas and the provider's policies apply. The app displays actual returned probe location/network details and does not label local anycast queries as remote city measurements. The result is a sample of DNS answers, not proof that every worldwide cache has updated. Stopping the local worker stops polling; a request already accepted by the remote service may still finish and remain available there. Service terms: https://globalping.io/terms/terms-of-use Service privacy: https://globalping.io/terms/privacy-policy
Ping sends four ICMP echo requests to the target with a one-second reply timeout. Traceroute sends route-discovery probes toward the target, limited to thirty hops with a one-second timeout per reply. It also sends PTR/reverse DNS queries for responding hop IPs through the configured resolver. A hostname target first requires DNS resolution. Resolver operators see the requested names and query metadata; responding routers and the destination can see probe traffic/source addresses. These actions do not upload a full device inventory or perform a bandwidth benchmark.
IP Configuration reads ipconfig /all output, including local adapter identities, IP and DNS settings, DHCP details and physical addresses exposed by Windows. Netstat reads numeric local/remote connection addresses, ports, connection states and process IDs using netstat -ano. It does not intentionally resolve endpoint names or inspect packet contents. Quick Wi-Fi / Network Check reads netsh wlan show interfaces, including any reported SSID, BSSID, adapter, authentication, radio, channel, signal and link-rate details. It does not read Wi-Fi passwords, change the active connection or launch a network benchmark. Windows Location permission may limit which wireless fields are available. These three local snapshots do not request an external diagnostic service.
Tool results remain in the screen's session memory locally. The app does not send them to the publisher, write a diagnostic-history file or automatically export them. The Globalping service also holds its remote measurements and results as described above. The entered targets and returned IP, adapter, process or wireless details can be sensitive; they remain part of any screenshot or output the user chooses to share. Normal Windows command and DNS activity may leave operating-system records according to local policy.
CLEAR RDP ADDRESS HISTORY: CONFIRMED LOCAL DELETION
Opening this tool displays a Yes/No confirmation with No as the default; no deletion happens without Yes. Clear History displays that confirmation again for a later attempt. It refuses to proceed while an mstsc (Remote Desktop Connection) process is open. The operation runs as the current Windows user and is limited to:
- Values named MRU followed only by digits in HKCU\Software\Microsoft\Terminal Server Client\Default.
- The current user's mstsc taskbar Jump List file: %APPDATA%\Microsoft\Windows\Recent\AutomaticDestinations\ 1bc392b8e104a00e.automaticDestinations-ms
- Only the remembered address values in full address:s: and alternate full address:s: fields in the current user's Documents\Default.rdp. Other bytes, file encoding and unrelated settings are preserved.
Removing that Jump List also removes connections pinned inside it. The pinned Remote Desktop application icon remains. The operation does not delete saved passwords/Credential Manager data, saved usernames, the Servers registry branch, unrelated Default.rdp settings, other saved .rdp files, browser history or other applications' Jump Lists. The two Default.rdp address fields are cleared to remove the last Computer-box address. The tool refuses read-only, signed, locked or malformed files, actual symbolic links and unsupported reparse tags instead of forcing a rewrite. Recognized Windows Cloud Files placeholders, including OneDrive, are supported. A read-only fsutil query identifies the tag; no reparse point or synchronization setting is removed or changed. An update is read back for verification; if a write fails, the operation tries to restore and verify the original bytes and reports any failure. No persistent backup of cleared history is created. New connections are remembered normally.
The action makes no direct network request and creates no backup. Reading a cloud placeholder may hydrate it through its configured sync provider; the provider may then synchronize the address edit normally. The action does not promise removal of independent Windows/security logs. Results describe partial failures rather than reporting an incomplete operation as a full success. Closing a screen does not restore history already removed. This is the only new tool that deletes user data, and it acts only after that explicit confirmation.
STORAGE AND SYSTEM CHANGES
Readings and rolling session statistics remain in process memory. This version does not save or export diagnostic history, capture packet contents, provide analytics/advertising/account login, or perform automatic update checks. Trial/registration records are stored as described above. It does not change firewall rules, system DNS, network profiles, routing tables or MTU settings. The confirmed RDP history action changes only the address history items described above. Public probes are diagnostics only.
INSTALLATION AND BUILD RECORDS
Setup installs the application, runtime configuration, icon, two Internet Health PowerShell scripts, two Mesh PowerShell scripts, two Port PowerShell scripts, two LAN PowerShell scripts, the Tools runtime scripts, this policy and uninstall files in the chosen folder. It creates Start Menu shortcuts, an optional desktop shortcut and a Windows Apps uninstall entry. Setup creates a local log in the Windows temporary folder. The separate source builder writes output and logs in its extracted folder. Logs may contain local paths and environment details. Review them before sharing. The publisher does not automatically receive them. Algorithm checks use synthetic data and make no diagnostic network requests or real RDP-history changes. The source builder now integrates Azure signing using the existing installed Microsoft signing prerequisites; it downloads no tools. Authentication, signing and timestamping contact Microsoft/Azure and certificate/timestamp services, which receive normal account/request/file-digest metadata according to their policies. Sign-in occurs on the build PC. Account credentials are not embedded in this source package. These build-only tools are not installed by the application's installer. See docs\SIGNING-PLAN.txt for the signing flow.
Windows, PowerShell logging, security products, DNS and other operating-system services may independently retain records according to their settings.
UNINSTALLATION AND CONTACT
Use Windows Settings > Apps > Installed apps (Apps & features on Windows 10) or the Start Menu uninstall shortcut. Uninstall removes its installed files, shortcuts, Windows uninstall registration and LicenseState\registration.dat while preserving unrelated files. The trial records described above remain, so reinstalling does not reset trial eligibility. Separately extracted source/build folders and Windows temporary logs are not removed. Publisher website and privacy contact: https://aicreatenow.com/