Where is basetsd.h included

We will take a look at it ad let you know. Sorry, something went wrong. Closing as there is no activity for a month. Please open a new issue if there is a problem with the build. Skip to content. Star New issue. Jump to bottom. Build error on Win Cannot open include file: 'basetsd. How to Fix basetsd. Step 1: Restore your PC back to the latest restore point, "snapshot", or backup image before error occurred.

In the search results, find and click System Restore. Follow the steps in the System Restore Wizard to choose a relevant restore point. Restore your computer to that backup image. If the Step 1 fails to resolve the basetsd. Step 2: If recently installed C-Free or related software , uninstall then try reinstalling C-Free software. After the software has been fully uninstalled, restart your PC and reinstall C-Free software.

If this Step 2 fails as well, please proceed to the Step 3 below. In the Windows Update dialog box, click " Check for Updates " or similar button depending on your Windows version If updates are available for download, click " Install Updates ". After the update is completed, restart your PC. Please follow the steps below to download and properly replace you file: Locate your Windows operating system version in the list of below "Download basetsd.

Click the appropriate "Download Now" button and download your Windows file version. Download basetsd. A handle to a hook. A handle to an icon.

A handle to a menu. A handle to a metafile. The return codes used by COM interfaces. A handle to a region. A handle to a window station.

A handle to a window. A signed integer type for pointer precision. Use when casting a pointer to an integer to perform pointer arithmetic. A language identifier.

For more information, see Language Identifiers. A locale identifier. For more information, see Locale Identifiers. A locale information type. For a list, see Locale Information Constants. A language group identifier.

For a list, see EnumLanguageGroupLocales. A signed long type for pointer precision. Use when casting a pointer to a long to perform pointer arithmetic. For more information, see Windows Data Types for Strings. A pointer to a constant null-terminated string of bit Unicode characters. A pointer to a null-terminated string of bit Unicode characters.

A bit pointer. On a bit system, this is a native pointer. On a bit system, this is a truncated bit pointer. On a bit system, this is a sign-extended bit pointer. A handle to a service control manager database. For more information, see SCM Handles. A lock to a service control manager database. A handle to a service status value. The maximum number of bytes to which a pointer can point. Use for a count that must span the full range of a pointer. Use within a structure that contains a pointer and two small fields.

An unsigned INT. If you have no plans for your code to ever be recompiled for a bit box then ignore it. A couple of things I didn't understand. Are you saying that compiling my program with the new windows include files can result in bit code without me making any changes in my code to make that happen, or are you saying that if I convert to the new types the code will then be usable in both cases.

I gather that, if, and only if, I want to uses the new macros and types do I need to include basetsd. Thanks, I guess the wizzard must have added it to my project?? There is no "overhead" or impact on your code. No, you can "write" code that can be compiled with a bit compiler or a bit compiler without error or warnings. Just open the header and take a look at the code. It is self-explanitory. So removing it is likely safe.