A clear start.
Useful answers.

Use 64-bit Windows with IIS, .NET Framework 4.8 or newer, and administrator access. Available measurements depend on installed Windows and IIS components and the fields already enabled in your W3C logs. Setup does not install IIS or enable missing capabilities.

Installation and monitoring require administrator access for local measurements and lifecycle management. The application creates its own local monitoring engine and worker task. That access is not used to change your websites, logging fields, DNS or firewall rules.

No. Choose trial or registered access, select the IIS sites and recording duration, and start monitoring in the application. Installation alone does not start the free trial.

Some information depends on Windows components, permissions and existing IIS logging fields. A missing counter or unavailable active-request snapshot is not proof of zero activity. Check the application's compatibility guidance and the components and fields available on the server.

Monitoring reads existing logs, configuration and Windows measurements. It does not change sites, pools, bindings, logging fields, website files, DNS, firewall rules or original IIS logs. It creates its own monitoring files, worker and licensing state.

Only when you choose Start Two-Day Free Trial in the application. It lasts 48 elapsed hours, including periods when the application is closed. Installing alone does not start it, and no payment is required to begin the trial.

Yes. Enter your 10-digit license key at first launch. You can also activate during the trial from Safety & Help, or after the trial expires. Initial activation requires an Internet connection and licensing-service approval.

No. Complete the purchase using the Stripe checkout, then enter the delivered 10-digit key in IIS Monitor 3. For questions about a purchase or a missing key, contact [email protected].

One lifetime license for the activated computer, paid once. Registration is bound to that computer. Hardware or Windows changes can require reactivation. See the publisher's purchase and refund policy for purchase-related requests.

Recording stops and finalization is requested. Further monitoring needs a valid registration. Existing saved results remain on disk, and you can enter a key after the trial has ended.

Initial activation needs Internet access. After approval, normal access checks use the saved local registration without routine licensing-server revalidation.

No. Ordinary uninstall retains separate trial and registration records. If access is blocked by missing, damaged or inconsistent licensing records, contact support instead of deleting licensing state.

Select the IIS sites to include, choose 1, 6, 12, 24, 48, 72 or 168 hours, and select Start Monitoring. Use Stop & Finalize when you're ready to end a session early and review the reports.

The duration selector supports up to 168 hours. A session extending past your 48-hour trial deadline requires a registered installation. Storage, system availability and interruptions still limit recording.

Minimizing keeps the monitoring worker running. Stop & Finalize or a normal application close finalizes the session and removes the product-owned worker. Reboots and Windows failures can interrupt coverage.

Normally in the AI Creations Now IIS Monitor Results folder on your Desktop. You can review CSV, TXT and JSON reports and package a finalized session as a ZIP. The application does not provide native PDF or HTML report export.

Use the application's log-management controls to remove completed product-owned sessions and ZIPs with confirmation. Active or uncertain recording states are protected from that deletion workflow. Original IIS logs are not deleted by those controls.

No. The application uses a 1,000 MB ceiling for its retained monitoring storage, including sessions, packages and its working files. This limit does not cap or delete original IIS logs.

Ordinary uninstall preserves the Desktop results folder and separate license and trial records. It removes installed application files and shortcuts after product-owned recording has stopped and finalized.

Core telemetry updates every three seconds. Detailed live tables publish up to once a minute when changed, and at finalization. Different measurements do not all have the same update interval.

No. Connection counts are server measurements, not unique human visitor counts. One user, browser or proxy can establish multiple connections.

No. Requests served completely from an edge cache do not reach your IIS origin. The app shows origin evidence and separate server network measurements. External traffic can include public connections from Cloudflare proxies.

Physical adapter traffic can include other applications, protocols and LAN activity. Completed IIS totals come from existing selected-site W3C request records. These scopes differ, and the totals are not an exact ISP billing calculation.

Completed request detail comes from IIS records after processing is recorded in the logs. This is not a byte-by-byte progress display for an unfinished transfer.

Individual request detail can be sampled at high load. Cumulative totals include accepted W3C records. Missing log fields and unavailable counters are not filled with invented values.