70-688 Supporting Windows 8.1 Exam Guide
Exam 70-688 validates administration and support skills for Windows 8.1 environments, especially installation and application strategy, resource access, networking, and compatibility troubleshooting. It is aimed at IT professionals working with Windows desktop deployment and support rather than at candidates seeking a current role-based credential. This guide helps you decide whether the legacy exam matches your objective, identify the skills to study, and build a practical lab-based preparation plan without relying on unauthorized question material.
What 70-688 is designed to validate
70-688 is associated with supporting Windows 8.1: choosing installation approaches, deploying and maintaining applications, preserving access to organizational resources, and troubleshooting connectivity. Microsoft’s change notice identifies its original title as “Managing and Maintaining Windows 8” and its updated title as “Supporting Windows 8.1.”
Microsoft’s certification roadmap labels exam 688 “Supporting Windows 8.1” and places it alongside exam 687, “Configuring Windows 8.1,” in the Windows certification path. That pairing is useful context: 70-688 is oriented toward support and maintenance decisions, while the companion exam is presented as the configuration-focused part of the path.
The subject matter belongs to an older Windows certification track. Microsoft’s later article about mapping 70-xxx exams to role-based certifications explains that Microsoft introduced new role-based certifications and provided an alignment table for certain earlier exams. The supplied evidence does not identify a replacement certification for 70-688, so candidates should verify the current credential catalogue before committing to a booking.
Who should consider this exam
The best fit is an administrator or support specialist who must keep Windows 8.1 desktops, applications, network access, and deployment processes working. Candidates should be comfortable diagnosing a problem from symptoms, selecting an appropriate Windows feature, and explaining why one remediation is safer or more suitable than another.
A candidate coming from desktop support may already understand user incidents but need stronger coverage of imaging, Windows PE, virtualization, compatibility shims, and network troubleshooting. A deployment professional may have the reverse gap: strong build processes but less practice with application behavior, resource access, or IPv6 and name-resolution faults.
The exam is less suitable if your objective is a current Windows endpoint credential or a modern cloud-management pathway. The official sources supplied here describe Windows 8.1 material and a legacy certification roadmap, not current exam availability, retirement status, booking options, or a modern replacement. Treat the decision to pursue it as a catalogue-verification task, not an assumption.
Which skills are measured
The change notice identifies two objective domains with explicit weight ranges: “Design an installation and application strategy” is weighted 25%–30%, and “Maintain resource access” is weighted 25%–30%. These are the only blueprint percentages established by the supplied research, so do not infer the weighting of other topics from their apparent length in a study guide.
The installation portion includes Windows To Go, operating-system virtualization, native VHD boot, multiboot, upgrade-versus-migration decisions, Windows PE customization, and desktop-image management. Study these as connected deployment choices rather than isolated definitions: the practical question is usually which approach fits the device, operating system state, application requirements, and recovery needs.
The application portion includes Application Compatibility Toolkit shims and compatibility databases, Hyper-V, RemoteApp, App-V, User Experience Virtualization, Windows Intune, Office 365, Windows Store apps, AppLocker, and application sideloading. You should be able to distinguish an application remediation from an application delivery method and from an application-control policy.
The supplied change notice also identifies networking skills covering IPv4 and IPv6 troubleshooting, transition technologies, name resolution, Peer Name Resolution Protocol, DNSSEC, wireless networks, Windows Firewall, and IP security. Build a troubleshooting sequence for these topics instead of memorizing product names: establish scope, inspect addressing and resolution, test the path, then review filtering and policy.
“Maintain resource access” is a broad support objective, not merely a file-sharing topic. Prepare to reason about network reachability, wireless access, name resolution, firewall behavior, IP security, and the effect of identity or policy choices on the user’s ability to reach a resource. Keep the stated domain label beside its 25%–30% weighting in your notes.
How to use the official preparation material
Microsoft’s Windows download page lists a file named “Preparing for the Supporting Windows 8.1 Exam (70-688).zip” and shows the package size as 3.9 GB. The page says the training modules are separate .zip files and instructs learners to download and extract the contents to view them.
Use that package as the organizing spine of your study. First inspect its module names and map each module to the change notice’s objectives. Then create a checklist with four columns: concept, hands-on task, evidence of understanding, and unresolved question. This prevents passive video watching from being mistaken for exam readiness.
The same Microsoft page lists Windows 8.1 as a supported operating system for the online-learning courses. That is a course-system detail, not evidence that a live exam is currently offered or that a particular lab configuration reproduces an examination environment. Use the material to learn the technology, then confirm current exam information through Microsoft’s credential pages.
Build a study lab around decisions
A small isolated lab is more valuable than a large collection of notes because 70-688 topics are operational. Create repeatable exercises for deployment, application compatibility, and networking, and record the initial symptom, diagnostic evidence, change made, and verification result. Do not use production systems for experiments involving images, boot configuration, firewall policy, or compatibility databases.
For installation strategy, compare a clean installation, an upgrade, and a migration in written scenarios. Add exercises for native VHD boot, multiboot, Windows To Go, operating-system virtualization, and Windows PE customization. The goal is not to reproduce a particular question; it is to explain the trade-off in each scenario and identify the dependencies that could invalidate an otherwise attractive option.
For application support, create a compatibility test plan. Start with a legacy application that reports an operating-system or runtime problem, test it under the correct user context, and document whether a shim or compatibility database is appropriate. Microsoft’s compatibility documentation states that the Application Compatibility Toolkit installs both 32-bit and 64-bit versions of Compatibility Administrator; the version must match the application architecture.
For networking, deliberately separate failures. Test an address configuration problem, a name-resolution problem, a wireless connection problem, and a firewall or IP-security rule problem. For each one, write the smallest set of tests that distinguishes the likely causes. Include both IPv4 and IPv6 reasoning, as well as transition technologies and DNSSEC concepts listed in the official objectives.
Keep snapshots or exportable configurations where possible, and reset the lab after each exercise. A lab notebook should contain commands, settings, expected results, and rollback steps. This makes revision faster and exposes gaps that a glossary cannot reveal.
Application compatibility practice
Compatibility fixes work by addressing specific behavior differences between Windows versions, so study the symptom-to-fix relationship rather than treating every shim as interchangeable. Microsoft documents fixes for issues such as incorrect operating-system version detection, legacy display behavior, elevation, library loading, and registry behavior.
For example, the WinxxRTMVersionLie fix addresses applications that fail because they do not find the expected Windows operating-system version, while DirectXVersionLie addresses an application that does not find the expected DirectX version. The version-lie family returns suitable version information to the application; it does not repair every compatibility failure.
Microsoft also documents ForceLoadMirrorDrvMitigation, which loads the Windows 8 mirror-driver mitigation when it is not automatically applied, and EmulateSortingWindows61, which emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs. These examples illustrate why the observed symptom must drive the selected fix.
Test a repaired application under the destination user account. Microsoft warns that launching Compatibility Administrator with elevated privileges can affect virtualization and redirection behavior, so an administrator-only test may not represent the user’s actual result. Record both the architecture of the application and the security context used for validation.
Deployment and application delivery practice
Separate the lifecycle questions before selecting a technology: how the operating system is installed, how the application is delivered, how user settings follow the user, and how execution is controlled. This structure helps distinguish Windows PE and image management from App-V, RemoteApp, User Experience Virtualization, AppLocker, and sideloading.
Write scenario cards that require a choice among local installation, remote application access, virtualization, packaged delivery, or policy control. For each card, state the user requirement, connectivity assumption, application dependency, management boundary, and failure response. Then explain why the rejected alternatives do not fit.
Include Windows Intune and Office 365 in your revision because they appear in the application-related skills in the change notice. Do not reduce those topics to brand recognition. Focus on the administrative purpose described by the scenario and on how the service or product interacts with desktop application management and user access.
For Windows Store apps and application sideloading, study the difference between obtaining an app through the expected store experience and deploying an app through an organizational process. For AppLocker, focus on the control objective and the consequences of an overly broad or overly narrow rule. Use only documented lab scenarios, not purported live questions.
A practical four-stage roadmap
Use a staged plan: establish the blueprint, learn the technology, perform targeted labs, and validate decision-making. The calendar should reflect your existing Windows experience and lab access rather than an invented fixed duration. Move forward only when you can explain and test a topic, not simply recognize its terminology.
Stage one is an inventory. Read the official change notice, copy its objective names into a checklist, and mark each skill as familiar, partly understood, or untested. Give particular attention to the two explicitly weighted domains: “Design an installation and application strategy” at 25%–30% and “Maintain resource access” at 25%–30%. Keep networking as a separate checklist because it crosses several support scenarios.
Stage two is structured learning. Work through Microsoft’s preparation package and use the previous-versions documentation for detailed compatibility behavior. After each module, write a short decision rule in your own words. Examples include “match Compatibility Administrator architecture to application architecture” and “verify the repaired application in the destination user context.” Rules should be testable in the lab.
Stage three is hands-on consolidation. Perform one deployment exercise, one application compatibility exercise, one application-delivery exercise, and several isolated network fault exercises. Rebuild or reset the environment and repeat the tasks without following notes. When an exercise fails, classify the failure as a knowledge gap, an incorrect assumption, or a lab-configuration issue.
Stage four is readiness review. Take the objective checklist and explain each item aloud or in writing using a symptom, decision, action, and verification structure. Any topic that produces a definition but no procedure returns to the lab. Any topic that produces a procedure but no rationale returns to the official documentation.
Suggested sequence for the first pass
Start with installation strategy because it provides the deployment context for the rest of the study. Follow with image management and Windows PE, then move to application compatibility and delivery technologies. Study resource access after you can describe the endpoint state, because many support scenarios depend on how the device and application were deployed.
Finish the first pass with networking and security controls. Review IPv4 and IPv6 together, then work through name resolution, wireless connectivity, Windows Firewall, IP security, transition technologies, Peer Name Resolution Protocol, and DNSSEC. The sequence should move from basic reachability to resolution and policy so that each later test has a clear purpose.
At the end of the first pass, produce a one-page map linking each objective to one lab task and one Microsoft reference. This map is more useful than a long, unclassified list of commands because it shows whether every objective has both conceptual and operational coverage.
How to allocate revision time
Allocate revision by weakness first, then by the official weight ranges. The two domains explicitly listed at 25%–30% deserve reliable coverage, but a candidate should not ignore networking or application topics simply because the supplied evidence does not provide their percentages. No unsupported percentage should be used to rank those remaining areas.
Use active recall for terminology and troubleshooting rehearsals for procedures. A useful revision block begins with a closed-book diagnosis, continues with documentation checking, and ends with a clean rerun of the fix. Keep separate error logs for deployment choices, application compatibility, and resource access so recurring mistakes remain visible.
In the final review, prefer breadth with evidence over obscure detail. You should be able to identify the relevant technology, state its purpose, select a reasonable action, and explain how you would verify the result. If a detail is not supported by the official material, do not turn a guess into a study fact.
Compatibility troubleshooting details worth mastering
Compatibility troubleshooting rewards precise symptom matching. Microsoft’s documentation explains that compatibility fixes address problems caused by changes between Windows versions, including UAC restrictions, version detection, legacy graphics behavior, registry access, and other application assumptions. Learn the underlying failure pattern first, then associate the documented fix with it.
The Win7RTM and Win8RTM layers provide an application with Windows 7 or Windows 8 compatibility-mode behavior. The version-lie fixes instead return appropriate operating-system version information when an application checks for a specific version. Those are related but distinct approaches: one emulates a broader environment, while the other targets version reporting.
RunAsHighest enables an application to run by using the highest available permissions, and Microsoft describes it as equivalent to specifying highestAvailable in an application manifest. RelaunchElevated addresses installers, uninstallers, or updaters that fail when started from a host application. Do not select an elevation-related fix merely because the symptom says “access denied”; establish what process is failing and how it was launched.
LoadLibraryRedirect forces an application to load system versions of libraries instead of redistributable versions shipped with the application. InstallComponent prompts the user to install .NET 3.5 or .NET 2.0 because .NET is not included with Windows 8. These cases require different remedies, so record the missing component or loading behavior before changing configuration.
The documentation also describes SystemMetricsLie, which replaces SystemMetrics and SystemParametersInfo values with values from previous Windows versions, and SetupCommitFileQueueIgnoreWow, which addresses a 32-bit setup program that fails because it requires 64-bit drivers. Use these examples to practise identifying the API, installer architecture, and dependency involved in a failure.
A common mistake is testing only as an administrator. Microsoft states that repaired applications should be tested under the destination user account to verify that a fix addresses the issue. Another is using the wrong Compatibility Administrator architecture; Microsoft says the 32-bit version is for 32-bit applications and the 64-bit version is for 64-bit applications. Make both checks part of your lab procedure.
Resource access and network diagnosis
Resource-access questions should be approached as layered diagnosis: confirm the local interface, validate addressing, test name resolution, test the route, and then inspect wireless, firewall, or IP-security controls. This sequence prevents a policy change from being used to mask a DNS or IPv6 configuration problem.
For IPv4 and IPv6, practise identifying whether the endpoint has a usable address, the correct gateway relationship, and a path to the target. Then separate a failure to reach an address from a failure to resolve a name. Add transition technologies to your notes as mechanisms that can affect communication between protocol environments, not as interchangeable replacements for basic addressing checks.
Name resolution deserves its own decision tree. Ask whether the client is using the expected resolver, whether the name is internal or external, whether an address is returned, and whether the returned address is reachable. Include DNSSEC in the policy and validation discussion, while keeping name-resolution failure distinct from packet filtering.
Wireless troubleshooting should begin with association and configuration before moving to authentication or policy. For Windows Firewall and IP security, identify the direction, profile or policy context, protocol, port, and scope involved. A rule that permits one test does not prove that the intended least-privilege policy is correct.
Peer Name Resolution Protocol is another case where purpose matters more than memorized expansion. Place it in a scenario involving peer discovery and compare that scenario with conventional DNS resolution. Your study notes should say what the technology is expected to solve and what evidence would show that it is not the current cause.
Common preparation mistakes
The most damaging mistake is treating a legacy exam as if its availability and relevance were current by default. The supplied sources establish its Windows 8.1 scope and historical roadmap context, but they do not establish current delivery, retirement, pricing, languages, prerequisites, score requirements, or appointment details. Verify those items through Microsoft before scheduling or paying.
Another mistake is studying feature names without practising selection. Knowing that Windows To Go, native VHD boot, Hyper-V, RemoteApp, App-V, and Windows Intune exist does not demonstrate that you can choose among them. Turn every feature into a scenario with constraints, then justify the decision and define a verification step.
Do not confuse an application symptom with an operating-system deployment problem. A legacy application may need a compatibility fix, a missing runtime component, an elevation adjustment, or a corrected library load. Reinstalling the operating system is not a diagnostic method. Capture the error, architecture, launch context, and affected API or dependency before changing the environment.
Avoid using unauthorized dumps or memorized question banks as a substitute for learning. They cannot establish that you understand the objective, may contain inaccurate or obsolete material, and do not provide a defensible way to practise administration. Use Microsoft’s preparation download, technical documentation, and controlled lab work instead.
A final mistake is leaving networking until the last revision session. Because the networking skills span IPv4, IPv6, resolution, wireless, firewall, IP security, and transition technologies, they require layered troubleshooting practice. Start early enough to repeat the diagnosis after resetting the fault.
Scheduling and delivery checks
Do not schedule 70-688 until Microsoft’s current credential and exam pages confirm that it can be taken and explain the applicable booking conditions. The supplied research does not provide a current exam status, delivery method, duration, question count, languages, price, prerequisite, passing score, or appointment date.
Use Microsoft Learn’s Browse Credentials page as the starting point for current credential information, then follow any official exam link associated with the credential or exam record. If the record is absent or unclear, use Microsoft Q&A for a focused question about the current status rather than relying on a third-party listing.
Separate historical facts from booking facts. The change notice says the updates were scheduled for January 2014 to cover Windows 8.1 tasks and terminology changes; that explains the exam’s scope but does not establish that an appointment is available now. The Microsoft download page lists the preparation package and its course details, but it is not a booking page.
Before committing, confirm the exact exam title and number, whether the content still matches your objective, the authorized registration route, identification and accommodation rules, and any applicable policies. Save the official page you checked and recheck it if your study period is long, because legacy-program information can change.
Final readiness test and next actions
You are ready to make a scheduling decision when you can map every listed skill to a procedure, diagnose a deliberately introduced fault, and explain why the chosen remedy fits the evidence. Readiness is not established by recognizing terms or recalling alleged exam questions; it comes from repeatable administration decisions supported by official documentation.
Complete these actions in order: verify the current exam record in Microsoft’s credential catalogue; download and extract the official 70-688 preparation package; turn the change notice into an objective checklist; build an isolated Windows 8.1 lab; practise installation, application, compatibility, and networking scenarios; and maintain an error log until each recurring gap is resolved.
For compatibility work, include architecture matching and destination-user testing. For networking, record the diagnostic layer at which the fault occurs. For deployment, write the constraints that caused you to choose Windows To Go, native VHD boot, virtualization, multiboot, Windows PE, or image management. For applications, distinguish delivery, compatibility, user-experience, and control decisions.
Finally, compare the exam’s Windows 8.1 focus with your actual career objective. If you need historical platform knowledge, 70-688 may provide a focused study target. If you need a current Microsoft credential, confirm the modern catalogue before investing further. That decision is as important as the study plan itself.
Conclusion
70-688 preparation should be treated as a technology-and-catalogue decision, not a memorization exercise. The official evidence points to Windows 8.1 support across installation strategy, applications, resource access, and networking, with “Design an installation and application strategy” and “Maintain resource access” each weighted 25%–30%. Use Microsoft’s preparation package and technical documentation, practise in an isolated lab, verify your troubleshooting logic, and confirm current availability and booking details before scheduling.
