dword-qword.gif

<div>
<div class="content wysiwyg-content">
How can I determine if an existing registry DWORD value is 32-bit or 64-bit?<br />
<br />
I need to create several DWORD values within the registry on a Server 2016 Datacenter OS.<br />
<br />
I am examining the registry on another Server 2016 Datacenter OS and am going to recreate these values within another Server 2016 Datacenter OS. However, while examining the registry on the server with these registry values I'm not sure if these DWORD values are 32-bit or 64-bit.<br />
<br />
Or should I just assume that because the operating system is Server 2016 Datacenter that all DWORD values should be created as 64-bit?<br />
<br />
Or how much of a difference does it make if the DWORD value is created as a 32-bit value when it should be a 64-bit value?
</div>
</div>


How can I determine if an existing registry DWORD value is 32-bit or 64-bit?

I need to create several DWORD values within the registry on a Server 2016 Datacenter OS.

I am examining the registry on another Server 2016 Datacenter OS and am going to recreate these values within another Server 2016 Datacenter OS. However, while examining the registry on the server with these registry values I'm not sure if these DWORD values are 32-bit or 64-bit.

Or should I just assume that because the operating system is Server 2016 Datacenter that all DWORD values should be created as 64-bit?

Or how much of a difference does it make if the DWORD value is created as a 32-bit value when it should be a 64-bit value?

Determine if existing DWORD value is 32 or 64-bit

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.