ANTO-LTG
Guides

Work tidily, from start to finish

Checklists and short how-tos so repair work stays consistent and customer data stays safe.

01

Before you start work

Record the physical condition, symptoms, accessories received, the owner's permission and the backup status before any risky action.

  • Confirm the scope and the cost.
  • Do not open personal data without permission.
  • Note the device condition and serial number only as far as needed.
02

Reinstalling Windows

Make sure the owner agrees to erasing data and that the installation media comes from an official source.

  • Verify the backup and the target disk.
  • Record the edition, the license and the drivers you will need.
  • Test updates, audio, network and input devices afterwards.
03

Hardware diagnosis

Run measured tests and explain the limits of the tools before concluding that a component is faulty.

  • Record the symptoms and the test results.
  • Back up before any risky test.
  • Do not run stress tests without permission and adequate cooling.
04

Handover

Check that the main functions work, explain what was done, and keep the customer's data protected.

  • Summarise the work and the parts replaced.
  • Hand over passwords the agreed way.
  • Delete temporary copies of data as agreed.
05

Verify a download

A file found on a website is not safe just because it was found there. Compare it with what the publisher states.

  1. Download only from the publisher's or vendor's own page.
  2. In PowerShell run Get-FileHash .\file.exe -Algorithm SHA256 and compare the result with the hash printed on the official page (the catalog shows it when the source publishes one).
  3. Run Get-AuthenticodeSignature .\file.exe to see who signed it. A missing signature is a reason to stop and ask.
  4. If anything differs, delete the file and do not run it.
06

Find drivers safely

Prefer the maker of the laptop or motherboard, then the chip vendor, and treat aggregator sites as leads only.

  1. Identify the exact model (Service Tag, serial number or the model printed on the device).
  2. Open the manufacturer's support portal from the Drivers page and pick your Windows version.
  3. If the maker has nothing, look for the chip vendor's page using the hardware ID.
  4. Never take a file from a driver-aggregator site: they gate files behind codes and cannot tell you who built them.
07

Run the generated WinGet script

The script is plain text you can read. It installs only the listed packages and asks you to type YES first.

  1. Open the downloaded .ps1 in an editor and read it.
  2. Open PowerShell in the folder that contains it. If scripts are blocked, allow them for this window only: Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned.
  3. Optionally run .\anto-ltg-install.ps1 -DryRun first to see the commands without installing.
  4. Run .\anto-ltg-install.ps1, check the plan, type YES, and read the failed-package report at the end.
08

Read a hardware ID

Hardware IDs tell you who made a chip, even when Device Manager shows "Unknown device".

  1. Device Manager, right-click the device, Properties, Details, Hardware Ids.
  2. VEN_8086 (PCI) is Intel, VEN_10EC is Realtek, VID_0403 (USB) is FTDI. The Drivers page decodes the vendor part for you.
  3. To list devices with problems in PowerShell: Get-PnpDevice -PresentOnly | Where-Object Status -ne 'OK'.
  4. Or run the read-only report script on the Drivers page and paste its output there.
These guides are general. Follow the manufacturer's documentation and the safety procedures that fit the device and the job.