Checked and Free Build Differences
There are two distinct builds of the NT-based operating systems that are available: free (retail) and checked (debug). There is a third option, called a partial checked build, that combines the elements of the two.
Checked builds were available on older versions of Windows, before Windows 10 version 1803. Use tools such as Driver Verifier and GFlags to check driver code in later versions of Windows.
Differences between the checked and free builds
This section lists some of the differences between the build choices.
The free build (or retail build)
The free build of Microsoft Windows is used in production environments. The free build of the operating system is built with full compiler optimizations. When the free build discovers correctable problems, it continues to run.
The distribution media that contain the free build of the operating system do not have any special labels—in other words, the CD or download that contains the free build is labeled with the Windows version name, without any reference to the type of build.
The checked build (or debug build)
The checked build of Microsoft Windows makes identifying and diagnosing operating-system-level problems easier.
The checked build differs from the free build in the following ways:
Many compiler optimizations (such as stack frame elimination) are disabled in the checked build. This makes it easier to understand disassembled machine instructions, and therefore it is easier to trace the cause of problems in system software.
The checked build enables a large number of debugging checks in the operating system code and system-provided drivers. This helps the checked build to identify internal inconsistencies and problems as soon as they occur.
A partial checked build (or partial debug build)
A partial checked build of Microsoft Windows is similar to the full checked build. The principal difference is that the partial checked build includes only the checked operating system image (the kernel) and the checked hardware abstraction layer (HAL). The rest of the Windows components come from the free (retail) build of Windows.
The partial checked build differs from the free and full checked builds in the following ways:
As in the full checked build, many compiler optimizations (such as stack frame elimination) are disabled. This makes it easier to understand disassembled machine instructions, and therefore it is easier to trace the cause of problems.
The partial checked build enables a number of debugging checks in the operating system code and HAL. However, the system-provided drivers come from the free (retail) build, so unless you explicitly install the checked versions of system-provided drivers, you do not get the additional benefits of the full checked build to identify and debug problems.
The partial checked build requires that you first install the complete free (retail) build of Windows. Using boot options, you can configure the computer to load either the checked or free components at boot time. You can then use a single computer for testing a driver with both checked and free builds of Windows.
Where to find a checked build of Windows
The downloads and distribution media that contain the checked build are clearly labeled as «Debug/Checked Build.» The checked build downloads contain the checked version of the operating system, plus the checked versions of HALs, drivers, file systems, and even many user-mode components. For information about obtaining the checked and partial checked builds, see Installing the Checked Build. For convenience, the checked versions of the kernel and HAL are provided in the /debug directory of the Windows Driver Kit (starting with WDK for Windows Vista).
When to use the checked build or partial checked build
You should always use the checked build at some point in during development when you need to test your driver. The checked build can expose problems in how the driver interacts with the operating system. No testing can be considered complete without testing that your driver is able to run in the checked build without issues.
Because the checked build contains fewer optimizations and more debugging checks than the free build, the checked build is both larger in size and slower to run than the free build. As a result, the free build is used in production environments unless it is necessary to use the checked build to identify serious problems.
As an alternative to a full checked build, you can configure a computer to use a partial checked build. This gives you the advantage of the checked build for debugging, and the better performance of the free build. For information about configuring your computer for a partial checked build, see Installing Just the Checked Operating System and HAL (For Windows Vista and Later).
For more complete testing of your driver when you are using a partial checked build, you also consider installing the checked versions of the related system-provided drivers. For example, if you are developing a lower disk filter driver, you should consider extracting and installing the checked build of Disk.sys and Storport.sys from the full checked build.
To verify that you are running the check build, follow the instructions in Step 4 — Restart the computer in Installing Just the Checked Operating System and HAL (For Windows Vista and Later)
Checked build windows 7
Вопрос
I have built (software wise) a laptop from scratch. An ASUS NX90jq. The owner did not want to build their computer using recovery discs, so they purchased an OEM copy of Window 7 64bit Ultimate. Since the store did not have a copy of Windows 7 64bit Ultimate OEM, they sold her the 32bit version, gave her a store copy of 64bit burnt on a DVD and tolder her to use the product key on the 32bit cover. OK all went fine and activated without any problem.
But despite being a fresh install of Windows 7 64bit Ultimate, her PC is BSOD-ing frequently. Analysing the BSOD, BCCODE, BCP1. etc codes, I have been made aware that this could be a ‘Checked Build’ of Windows 7, and may not be a ‘Free Build’. Not having any off the factory media to see the disc label, is there anyway I can tell if the copy of Windows I have installed is either Checked or Free?
Thanks and regards,
Ответы
Regarding this bugcheck code, please refer to the following link.
The following actions might prevent an error like this from happening again:
1.Download and install updates and device drivers for your computer from Windows Update.
2.Scan your computer for computer viruses.
3.Check your hard disk for errors.
TechNet Community Support
Все ответы
Please post the system sumary of System Information here.
Also, for BSOD issue, you may also upload the dump file to Skydrive and post the link. We will help you analyze it.
TechNet Community Support
Thank you very much for your response. Please find below additional information.
Processor: Intel(R) Core(TM)i7 CPU Q720 @ 1.60GHz 1.60GHz
System Type: 64-bit operating system.
Windows 7 Ultimate 64 Bit
Summary of crash report
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Additional information about the problem:
OS Version: 6_1_7601
Files that help describe the problem:
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
I have disabled many addon in Outlook 2010 SP1 and the BSOD hasn’t come back as yet. Hope this can help out a bit more.
Thanks and regards,
Regarding this bugcheck code, please refer to the following link.
The following actions might prevent an error like this from happening again:
1.Download and install updates and device drivers for your computer from Windows Update.
2.Scan your computer for computer viruses.
3.Check your hard disk for errors.
TechNet Community Support
After running a program called memtest, I found the RAM to be very corrupt or damaged. Just 7% into testing the RAM when all the error started. There were lots of them. Took the laptop back to the store and had all the damaged modules replaced, now it works a real treat.
May I ask regarding Microsoft Windows Update and drivers, is it better to update your hardware drivers from the manufacturer’s site? Rather than the Windows Update site.
Thanks and regards,
To get back the original question as to whether it’s a free or checked build.
run systeminfo from an elevated cmd prompt.
What is on the OS Build Type Line:
For example mine shows — OS Build Type: Multiprocessor Free
Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights. VAMT — Volume Activation Management Tool — Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
Apologies for a late response.
Please see below details yielded by ‘systeminfo’;
Host Name: FAT-PIG
OS Name: Microsoft Windows 7 Ultimate
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: F-Fugly
Registered Organization:
Product ID: #####-OEM-#######-#####
Original Install Date: 18/12/2011, 4:14:37 PM
System Boot Time: 6/01/2012, 6:44:12 AM
System Manufacturer: ASUSTeK Computer Inc.
System Model: NX90Jq
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel
1600 Mhz
BIOS Version: American Megatrends Inc. NX90Jq.207, 27/01/2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-au;English (Australia)
Input Locale: en-us;English (United States)
Time Zone: (UTC+10:00) Canberra, Melbourne, Sydney
Total Physical Memory: 12,213 MB
Available Physical Memory: 10,360 MB
Virtual Memory: Max Size: 18,355 MB
Virtual Memory: Available: 16,510 MB
Virtual Memory: In Use: 1,845 MB
Page File Location(s): D:\pagefile.sys
Domain: WORKGROUP
Logon Server: \\FAT-PIG
Hotfix(s): 54 Hotfix(s) Installed.
I’ve removed the hot-fix and network adapter information from the list. And yes the Host Name and Registered Owner are the actual names requested by the laptop owner, at their request. Just in case anyone wishes to complain.
Where can I get Windows checked build?
I’m developing a file system driver.
I use free build Windows as a target machine.
If I could get a checked build of Windows, I think I get more convenient. Isn’t it.
But I do not know even where I can get it. Does it need a cost?
And what are the benefits I can get, when I use it.
1 Answer 1
Checked builds are available to MSDN subscribers from the MSDN download website.
The benefits are that when you attach a kernel debugger to debug your driver, you will gets lots of extra debugging information sent to the debug console, especially if you call any function with invalid parameters, it will be caught closer to the actual error because every function does parameter checking (that’s the checked part of checked build) and print a warning.
And a description of one of the checked builds available on MSDN:
Windows 7 Checked/Debug Build (x86) — DVD (English)
File Name: en_windows_7_checked_build_dvd_x86_398742.iso
Date Published (UTC): 8/14/2009 9:55:36 AM
Last Updated (UTC): 5/21/2010 8:22:29 AM
Available to Levels: MSDN OS (VL); VS Pro with MSDN Pro (VL); VS Pro with MSDN Premium (Empower); MSDN OS (Retail); Developer AA; VS Pro with MSDN (Retail); MSDN Universal (Retail); VSTS Team Suite (VL); VSTS Architecture (VL); VS Premium with MSDN (MPN); VSTS Test (VL); VS Pro with MSDN Premium (MPN); MSDN Universal (VL); VSTS Database (VL); VS Pro with MSDN Premium (Retail); VSTS Test (Retail); VSTS Development (Retail); VSTS Architecture (Retail); VSTS Team Suite (Retail); VSTS Database (Retail); BizSpark Admin; BizSpark; VS Pro with MSDN Embedded (Retail); VS Pro with MSDN Embedded (VL); VS Test Pro with MSDN (VL); VS Ultimate with MSDN (VL); VS Premium with MSDN (VL); VS Pro with MSDN (VL); VS Test Pro with MSDN (Retail); MSDN Essentials; VS Premium with MSDN (Retail); VS Ultimate with MSDN (Retail); MSDN for Action Pack; VS Ultimate with MSDN (MPN); VS Ultimate with MSDN (NFR FTE);