Module 02 · Tier 1 · SOP-002
One of the most common Tier 1 tasks — and one of the most commonly done wrong. By the end of this module you'll understand system requirements, admin rights, installation types, and how to verify the job is actually done.
// 1.1
Most failed installs come down to one of six causes. Knowing the cause before you start saves time and prevents making things worse.
| Failure Reason | What's Actually Happening |
|---|---|
| No admin rights | Wrong account type — the user doesn't have permission to install software. Most corporate environments require elevation. |
| System requirements not met | Missing RAM, old OS version, or incompatible CPU architecture (32 vs 64-bit). Always check before downloading. |
| Corrupted installer | Download was incomplete or corrupted. Re-download from the official source — never from a third-party mirror. |
| Conflicting software | Another version is already installed. Must uninstall old version first, including leftover registry entries. |
| Disk space too low | Not enough free space on the target drive. Most installs need more breathing room than the stated minimum. |
| Group Policy block | IT policy is actively preventing the install. Requires escalation or a proper software request through the correct channel. |
// 1.2
User Account Control is Windows' way of making sure you meant to make a change that affects the system. It's the prompt that says "Do you want to allow this app to make changes?"
Security FeatureWithout UAC, any program you run could silently install itself, change system settings, or add startup entries. UAC adds a speed bump that stops malware from doing the same thing.
Malware PreventionAlways read the prompt before clicking Yes. Check that the publisher name matches what you're installing. If it shows "Unknown" for known software, stop and verify the source.
Best Practice// 1.3
The format of an installer changes how you handle it. MSI installers are designed for enterprise deployment. EXE installers can be anything. Knowing the difference saves time.
| Type | What It Is | Notes |
|---|---|---|
| .msi | Windows Installer Package | Standard enterprise format. Can be deployed via Group Policy. Usually has the most reliable uninstall path. |
| .exe | Executable Installer | Can contain anything — an MSI wrapper, a custom installer, or a self-extracting archive. Most consumer software uses this format. |
| .appx / .msix | Microsoft Store Package | Modern app format used by Windows Store apps. Usually installed through the Store or PowerShell. |
| .zip | Manual Installation | Not a true installer. Requires copying files to a specific folder and sometimes manually adding to PATH. Handle with care. |
// 1.4
Use this procedure for any software installation request. Deviation requires documentation.
Before installing anything, confirm the request came from an authorized person. In a business environment, software installs often require manager approval or a service ticket. Ask: "Do you have a ticket number or approval for this?"
Verify on the vendor's page: OS version (Windows 10/11), RAM, disk space, and CPU architecture. On the user's machine: Settings → System → About for OS and RAM. Check This PC for disk space. Cross-reference before proceeding.
Never use third-party download sites. Go directly to the vendor's website. Verify the URL matches the official domain. Right-click the downloaded file → Properties → check the digital signature if available.
Right-click the installer → "Run as administrator." This ensures UAC elevation is handled correctly. If prompted by UAC, verify the publisher name matches the expected software vendor. Do not click Yes if the publisher shows "Unknown" for known commercial software.
Follow the installer prompts. Key decisions: install path (use default unless directed), components (install only what's needed). Decline any bundled third-party software — toolbars, browser add-ons, and other extras are never needed.
Open the application to confirm it launches. Check Start Menu or Desktop for the shortcut. Verify version: Help → About, or check Control Panel → Programs. Run a basic function test — open a file, check that core features work.
Record: software name, version, installation date, install path, and whether any special steps were required. Note any deviations from standard procedure. Close the ticket with status: Resolved.
// quick reference
| Error | Likely Cause | First Fix |
|---|---|---|
| Error 1603 | Fatal error during installation | Run as admin, clear %temp%, restart and retry |
| "Cannot access specified device" | File or path permissions blocked | Check AV isn't quarantining installer. Re-download. |
| "This app has been blocked" | SmartScreen or Group Policy block | Verify source. Check with IT manager before bypassing. |
| "Not enough disk space" | Drive is full | Check This PC. Clear temp files: Win+R → %temp% → delete contents |
| App installs but won't launch | Missing dependency | Check if Visual C++ Redistributable or .NET Framework update is needed |
// 3.1 — real-world scenarios
Work through each scenario. Think before you act. Document as you go.
A user submits a ticket: "I need Adobe Acrobat Reader installed on my laptop. I tried to run the installer but it says I don't have permission." You remote in and see UAC is showing an "Unknown Publisher" warning — and the file was downloaded from a site called adobe-reader-download.net.
A user calls because their newly installed application crashes immediately on launch. You remote in and see they're running a 64-bit Windows 11 machine but installed the 32-bit version of the software. They also have a previous version from two years ago still showing in Programs and Features.
A small business employee needs a specialized accounting tool installed. You run the installer and receive: "The installation of this application has been blocked by your system administrator." You've verified the installer is legitimate and from the official source.
// 3.2 — documentation practice
Use the format below and write the ticket note for Scenario 1.
| Field | Your Entry |
|---|---|
| Date / Time | |
| Software Requested | |
| Source URL Verified? | |
| Admin Rights Used? | |
| Installation Result | |
| Issues Encountered | |
| Steps Taken | |
| Resolution / Status |
// 3.3 — interview preparation
Employers at every level ask some version of these questions. Put the frameworks below into your own words.
"Walk me through how you handle a software installation request from start to finish."
Start with authorization → check system requirements → download from official source only → run as administrator → follow prompts declining bundled software → verify it launches and core functions work → document everything.
"A user says they downloaded software from 'a site they found on Google' and it's not working. What do you do?"
First, I treat this as a potential security issue before a tech issue. I'd check the download source, run the file through Windows Defender, and if anything looks suspicious, quarantine and escalate. Then I'd locate the official vendor site and start fresh with a legitimate installer.
"How do you handle an installation that keeps failing with Error 1603?"
Error 1603 is a generic Windows Installer error that usually points to permissions, a conflicting install, or a corrupted %temp% directory. My steps: run as admin, clear %temp%, check Add/Remove Programs for any existing version, restart the machine, retry. If it still fails, I check the Windows Installer log in %temp% for the actual root cause.
// module completion checklist
Check each item before marking this module complete.
// what comes next
Every module follows the same structure. The further you go, the more you'll realize you already know.