| Title | Category | Keywords |
| GAME_INSTALL_SCOPE Enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Games Explorer > Programming Reference > Enumerations > GAME_INSTALL_SCOPE Enumeration | Reserved for internal use only. |
| ACTCTX_SECTION_KEYED_DATA structure | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Isolated Applications and Side-by-side Assemblies > Side-by-side Assemblies Reference > Activation Context Reference > ACTCTX_SECTION_KEYED_DATA | Number of bytes in the structure referred to by lpData. Note that the data structures grow over time; do not access members in the instance data that extend beyond ulLength. Note that the data structures grow over time and you may receive an old format activation context data block; do not access members in the section global data that extend beyond ulSectionGlobalDataLength. |
| Installer.ProductInfo property | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Windows Installer > Windows Installer Reference > Automation Interface > Automation Interface Reference > Installer Object > ProductInfo Property | The ProductInfo property ("LocalPackage") does not necessarily return a path to the cached package. Maintenance mode installations should be not be invoked from the LocalPackage. The cached package is for internal uses only. |
| Language | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Windows Installer > Windows Installer Reference > Installer Database > Installer Database Reference > Database Tables > Column Data Types > Language | For primary language IDs, the range 0x200 to 0x3ff is user definable. The range 0x000 to 0x1ff is reserved for system use. For sublanguage IDs, the range 0x20 to 0x3f is user definable. The range 0x00 to 0x1f is reserved for system use. |
| MsiGetProductInfo function | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Windows Installer > Windows Installer Reference > Installer Functions > Installer Function Reference > MsiGetProductInfo | MsiGetProductInfo(INSTALLPROPERTY_LOCALPACKAGE) does not necessarily return a path to the cached package. The cached package is for internal use only. Maintenance mode installations should be invoked through the |
| MsiGetProductInfoEx function | Dev Center - Desktop > Docs > Windows Development Reference > Application Installation and Servicing > Windows Installer > Windows Installer Reference > Installer Functions > Installer Function Reference > MsiGetProductInfoEx | The MsiGetProductInfoEx function (INSTALLPROPERTY_LOCALPACKAGE) returns a path to the cached package. The cached package is for internal use only. Maintenance mode installations must be invoked through the |
| Header Files and System Components | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > About the Windows Core Audio APIs > Header Files and System Components | The Core Audio APIs are implemented in the user-mode system components Audioses.dll and Mmdevapi.dll. Client applications do not access the entry points in these DLLs directly. Instead, clients call the CoCreateInstance or CoCreateInstanceEx function to obtain the IMMDeviceEnumerator interface of the MMDeviceEnumerator class object. This object enumerates the audio endpoint devices in the system. The IMMDeviceEnumerator interface is part of the MMDevice API. From this interface, clients can directly or indirectly obtain the other interfaces in the MMDevice API, including the IMMDevice interface. IMMDevice represents a particular audio endpoint device. Through IMMDevice, clients can directly or indirectly obtain the device-specific interfaces in WASAPI, the DeviceTopology API, and the EndpointVolume API. For more information about CoCreateInstance and CoCreateInstanceEx, see the Windows SDK documentation. For more information about accessing the interfaces in the Core Audio APIs, see Enumerating Audio Devices. |
| IAudioClient interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > Programming Reference > Core Audio Interfaces > IAudioClient | Note In Windows 8 Release Preview, the first use of IAudioClient to access the audio device should be on the STA thread. Calls from an MTA thread may result in undefined behavior. |
| IAudioClient::Initialize method | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > Programming Reference > Core Audio Interfaces > IAudioClient > Initialize | Note In Windows 8 Release Preview, the first use of IAudioClient to access the audio device should be on the STA thread. Calls from an MTA thread may result in undefined behavior. |
| IAudioSessionEvents interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > Programming Reference > Core Audio Interfaces > IAudioSessionEvents | In implementing the IAudioSessionEvents interface, the client should observe these rules to avoid deadlocks and undefined behavior: |
| IControlChangeNotify interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > Programming Reference > Core Audio Interfaces > IControlChangeNotify | In implementing the IControlChangeNotify interface, the client should observe these rules to avoid deadlocks and undefined behavior: |
| IMMNotificationClient interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Core Audio APIs > Programming Reference > Core Audio Interfaces > IMMNotificationClient | In implementing the IMMNotificationClient interface, the client should observe these rules to avoid deadlocks and undefined behavior: |
| IAMTimelineObj::SetStartStop method | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > DirectShow Editing Services > DirectShow Editing Services C++ Reference > Interfaces For DirectShow Editing Services > IAMTimelineObj > SetStartStop | Do not set overlapping times on source objects within the same track. Doing so can cause undefined behaviors. |
| Creating Groups Compositions and Tracks | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > DirectShow Editing Services > Using DirectShow Editing Services > Constructing a Timeline > Creating Groups, Compositions, and Tracks | The second parameter to VTrackInsBefore specifies the priority of the virtual track. Priority levels start at zero. If you specify the value –1, the virtual track is inserted at the end of the priority list. If you specify a value where there is already a virtual track, everything from that point on moves down the list by one priority level. Do not insert a virtual track at a priority greater than the number of virtual tracks, because it will cause undefined behavior. |
| Setting Properties on Sources | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > DirectShow Editing Services > Using DirectShow Editing Services > Working with Sources > Setting Properties on Sources | The start and stop times, relative to the rest of the timeline. Call the IAMTimelineObj::SetStartStop method. Do not set overlapping times on source objects within the same track, or it will cause undefined behavior. |
| VIDEOINFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > DirectShow Reference > DirectShow Structures > VIDEOINFO | Never use this structure unless you are sure that you will use it only to store standard RGB formats. If you store anything other than standard RGB, the variable size of the bmiHeader structure will almost certainly cause problems, and you should use the VIDEOINFOHEADER structure instead. If you find it absolutely necessary to use the VIDEOINFO structure, do not access the TrueColorInfo, dwBitMasks, or bmiColors members directly. Instead, use the TRUECOLOR, COLORS, and BITMASKS macros to return the pointers to the color information. Which of these members is valid depends on the contents of the BITMAPINFOHEADER structure. |
| AM_SimpleRateChange structure | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > DirectShow Reference > Property Sets > Rate Change Property Set > AM_SimpleRateChange structure | If a sample spans the start time, and the new rate is incompatible, the behavior is undefined. The decoder may keep the sample or discard it, depending on the media. |
| Writing DirectShow Filters | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > DirectShow > Using DirectShow > Writing DirectShow Filters | If you are developing a filter for use in a Microsoft DirectShow filter graph, read the articles in this section. In general, you do not have to read this section if you are writing a DirectShow application. Most applications do not access filters or the filter graph at the level discussed in this section. |
| WAVEFORMATEXTENSIBLE Structure | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Legacy Audio and Video > DirectSound > Reference > Structures > WAVEFORMATEXTENSIBLE Structure | Reserved for internal use by operating system. Set to zero. |
| joySetCapture function | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Legacy Audio and Video > Windows Multimedia > Multimedia Reference > Multimedia Functions > joySetCapture | If the specified joystick is currently captured, the function returns undefined behavior. Call the joyReleaseCapture function to release the captured joystick, or destroy the window to release the joystick automatically. |
| WAVEFORMATEXTENSIBLE structure | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Legacy Audio and Video > Windows Multimedia > Multimedia Reference > Multimedia Structures > WAVEFORMATEXTENSIBLE | Reserved for internal use by operating system. Set to 0. |
| IMF2DBuffer::Lock2D method | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Microsoft Media Foundation > Media Foundation Programming Reference > Media Foundation Interfaces > IMF2DBuffer > Lock2D | If p is a pointer to the first byte in a row of pixels, p + (*plPitch) points to the first byte in the next row of pixels. A buffer might contain padding after each row of pixels, so the stride might be wider than the width of the image in bytes. Do not access the memory that is reserved for padding bytes, because it might not be read-accessible or write-accessible. For more information, see Image Stride. |
| Managing Synchronization Playlists | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Windows Media Player SDK > Windows Media Player Object Model > Player Control Guide > Working with Portable Devices > Managing Synchronization Playlists | _T("Not used"), // Do not access this one. |
| IWMPMetadataPicture::get_URL method | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Windows Media Player SDK > Windows Media Player Object Model > Windows Media Player Object Model Reference > Object Model Reference for C++ > Interfaces > IWMPMetadataPicture Interface > IWMPMetadataPicture::get_URL | This method is for internal use only. |
| IWMSCommandContext Interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Windows Media Services 9 Series > Programming Reference > Programming Reference (C++) > Custom Plug-in Interfaces (C++) > IWMSCommandContext Interface | Note: This interface is available only on Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; and Windows Server 2008.A Command Context contains name-value pairs that describe a request issued by a client and the response issued by the server. The server creates a command context entry for each line in a request or response header, and the IWMSCommandContext interface provides methods for retrieving or deleting the request or response. In addition to the methods inherited from IUnknown, the IWMSCommandContext interface exposes the following methods.MethodDescriptionEraseCommandRequestDeletes a client request by erasing all of the name-value pairs in the command context.EraseCommandResponseDeletes a server response by erasing all of the name-value pairs in the command context.GetCommandRequestRetrieves a pointer to an IWMSContextIWMSContext Interface containing a command request context. You can use the pointer to retrieve name-value pairs that describe a client request.GetCommandResponseRetrieves a pointer to an IWMSContext interface containing a command context. You can use the pointer to retrieve name-value pairs that describe a server response.GetPlaylistGenerationIDReserved for internal use.SetPlaylistGenerationIDReserved for internal use.See Also |
| IWMSContentDescriptionList Interface | Dev Center - Desktop > Docs > Windows Development Reference > Audio and Video > Windows Media Services 9 Series > Programming Reference > Programming Reference (C++) > Custom Plug-in Interfaces (C++) > IWMSContentDescriptionList Interface | In addition to the methods inherited from IUnknown, the IWMSContentDescriptionList interface exposes the following methodsMethodDescriptionAppendDescriptionAdds an IWMSContext interface containing a content description context to the description list.GetBroadcastidReserved for internal use.GetDescriptionCountRetrieves the number of content description contexts in the description list.GetDescriptionInLanguageRetrieves the content description context for a specific language.GetIndexedDescriptionRetrieves a specific content description context from the description list by index.GetPlaylistGenidReserved for internal use.RemoveAllDescriptionsRemoves all content description contexts from the description list.RemoveValueFromAllDescriptionsRemoves a specific property from all the content description contexts in the description list.SetBroadcastidReserved for internal use.SetPlaylistGenidReserved for internal use.SetValueOnAllDescriptionsSpecifies the value of a specific property in all the content description contexts in the description list.See Also |
| MSFT_DedupJobSchedule class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Data Deduplication API > Data Deduplication API Reference > Data Deduplication Management WMI API Reference > MSFT_DedupJobSchedule | This property is reserved for system use. |
| MSFT_DedupVolumeMetadata class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Data Deduplication API > Data Deduplication API Reference > Data Deduplication Management WMI API Reference > MSFT_DedupVolumeMetadata | This property is reserved for system use. This property is reserved for system use. |
| CVssWriter::Initialize method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Classes > CVssWriter > Initialize Method | Windows Server 2003 and Windows XP: Before Windows Server 2003 with SP1, this parameter is reserved for system use, and the caller should not override the default value. |
| VSS_BACKUP_SCHEMA enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Enumerations > VSS_BACKUP_SCHEMA | Reserved for system use. |
| VSS_SNAPSHOT_STATE enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Enumerations > VSS_SNAPSHOT_STATE | Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. |
| _VSS_VOLUME_SNAPSHOT_ATTRIBUTES enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Enumerations > _VSS_VOLUME_SNAPSHOT_ATTRIBUTES | Reserved for system use. |
| IVssAdmin interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssAdmin | Reserved for system use. |
| IVssCreateWriterMetadata interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssCreateWriterMetadata | Reserved for system use. Reserved for system use. |
| IVssCreateWriterMetadata::AddComponent method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssCreateWriterMetadata > AddComponent Method | Windows Server 2003 and Windows XP: Before Windows Server 2003 with SP1, this parameter is reserved for system use, and the caller should not override the default value. |
| IVssExamineWriterMetadata interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssExamineWriterMetadata | Reserved for system use. Reserved for system use. |
| IVssExamineWriterMetadata::GetFileCounts method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssExamineWriterMetadata > GetFileCounts Method | Reserved for system use. |
| IVssExpressWriter::CreateMetadata method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssExpressWriter > CreateMetadata Method | This parameter is reserved for system use. |
| IVssSnapshotMgmt interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Interfaces > IVssSnapshotMgmt | Reserved for system use. (Inherited from IVssSnapshotMgmt) Reserved for system use. (Inherited from IVssSnapshotMgmt) |
| VSS_COMPONENTINFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Structures > VSS_COMPONENTINFO | Windows Server 2003 and Windows XP: Before Windows Server 2003 with SP1, this member is reserved for system use. |
| VSS_VOLUME_PROTECTION_INFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Reference > Volume Shadow Copy API Structures > VSS_VOLUME_PROTECTION_INFO | Reserved for system use. |
| VSS Metadata | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Backup > Volume Shadow Copy Service > Volume Shadow Copy Service Overview > Using the Volume Shadow Copy Service > VSS Metadata | Caution: The specific details of the format and schema are for system use only. Developers should not attempt to modify or |
| DismPackageFeatureState Enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Deployment Image Servicing and Management (DISM) API > DISM API Reference > DISM API Enumerations > DismPackageFeatureState Enumeration | DismStateResolved //For internal use only |
| DFS_INFO_107 structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System > Distributed File System Reference > Distributed File System Structures > DFS_INFO_107 | This member is reserved for system use. |
| DFS_INFO_150 structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System > Distributed File System Reference > Distributed File System Structures > DFS_INFO_150 | This member is reserved for system use. |
| DFS_INFO_9 structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System > Distributed File System Reference > Distributed File System Structures > DFS_INFO_9 | This member is reserved for system use. |
| DfsrMachineConfig class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System Replication > DFSR WMI Classes > DfsrMachineConfig | Reserved for system use. Reserved for system use. Reserved for system use. |
| DfsrReplicatedFolderConfig class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System Replication > DFSR WMI Classes > DfsrReplicatedFolderConfig | This method is reserved for system use. This method is reserved for system use. Reserved for system use. |
| DfsrReplicatedFolderInfo class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Distributed File System Replication > DFSR WMI Classes > DfsrReplicatedFolderInfo | This method is reserved for system use. |
| Extensible Storage Engine Error Codes | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Error Codes | This error is for internal use only. Note This error is for internal use only. |
| JetGetTableInfo Function | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Functions > JetGetTableInfo Function | JET_TblInfoName retrieves the name of the table and stores it in pvResult. If the buffer is too small, the behavior is undefined. JET_TblInfoMostMany retrieves the name of the table and stores it in pvResult. If the buffer is too small, the behavior is undefined. |
| JetRetrieveColumn Function | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Functions > JetRetrieveColumn Function | This flag is for internal use only and is not intended to be used in your application. This flag is for internal use only and is not intended to be used in your application. |
| JET_INDEXCREATE Structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Structures > JET_INDEXCREATE Structure | Deprecated: After the language ID, it is possible to pass cbVarSegMac as a USHORT. The behavior is undefined if the USHORT is set both in szKey and if cbVarSegMac is set in the structure. |
| JET_OBJECTINFO Structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Structures > JET_OBJECTINFO Structure | The table is a System Table and is for internal use only. |
| JET_RETRIEVECOLUMN Structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Extensible Storage Engine > Extensible Storage Engine Reference > Extensible Storage Engine Structures > JET_RETRIEVECOLUMN Structure | This flag is for internal use only and is not intended to be used in your application. This flag is for internal use only and is not intended to be used in your application. |
| PARTITION_INFORMATION_GPT structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Local File Systems > Disk Management > Disk Management Reference > Disk Management Structures > PARTITION_INFORMATION_GPT | such as Disk Defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this |
| File Attribute Constants | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Local File Systems > File Management > File Management Reference > File Management Constants > File Attribute Constants | This value is reserved for system use. This value is reserved for system use. |
| Wow64DisableWow64FsRedirection function | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Local File Systems > File Management > File Management Reference > File Management Functions > Wow64DisableWow64FsRedirection | Note This value is for system use only. To avoid unpredictable behavior, do not modify this value in any |
| COPYFILE2_MESSAGE structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Local File Systems > File Management > File Management Reference > File Management Structures > COPYFILE2_MESSAGE | This member is reserved for internal use. This member is reserved for internal use. This member is reserved for internal use. This member is reserved for internal use. This member is reserved for internal use. This member is reserved for internal use. |
| FILE_ID_EXTD_DIR_INFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Local File Systems > File Management > File Management Reference > File Management Structures > FILE_ID_EXTD_DIR_INFO | This value is reserved for system use. This value is reserved for system use. |
| NormalizeAttributeValues Property | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > DOM > DOM Reference > XML DOM Properties > Second-Level DOM Properties > NormalizeAttributeValues Property | Changing the value of this property after a document is loaded results in undefined behavior. Set this property before loading the document. |
| (Deprecated) IXMLParser Interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > Helper APIs for MSXML > Helper API Reference [MSXML] > XML Helper Objects/Interfaces > (Deprecated) Push Model XML Parser/Node Factory > (Deprecated) IXMLParser Interface | When you call PushData with lastBuffer set to TRUE, you should not push any more data unless you first reset the parser. If you do, the behavior is undefined. |
| getLocalName Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getLocalName Method | ParametersnIndex[in] The attribute's index value.ppwchLocalName[out] The attribute's local name. ppwchLocalName should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchLocalName, you should make a deep copy.pcchLocalName[out] The length of the local name string.Return ValuesS_OK The value returned if the local name is returned successfully.E_FAIL The value returned if an internal error occurs.E_INVALIDARG The value returned if the local name cannot be found. |
| getName Method (C/C++) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getName Method (C/C++) | ppwchUri, ppwchLocalName, and ppwchQName should not be modified or deleted, because this can cause undefined behavior in the SAXp. If you want to preserve the value that was returned in on of the listed parameters, you should make a deep copy. |
| getQName Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getQName Method | ParametersnIndex[in] The attribute's index value.ppwchQName[out] The attribute's qualified name. ppwchQName should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchQName, you should make a deep copy.ppchQName[out] The length of the qualified name string or –1 (if zero-terminated).Return ValuesS_OK The value returned if the QName is returned successfully.E_FAIL The value returned if an internal error is reported.E_INVALIDARG The value returned if QName is not found. |
| getType Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getType Method | ParametersnIndex[in] The attribute's index value.ppwchType[out] The returned type of the attribute. ppwchType should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchType, you should make a deep copy.pcchType[out] The length of the returned type attribute string. Return ValuesS_OK The value returned if the attribute type is returned successfully.E_INVALIDARG The value returned for an invalid index or if no matching attribute is found.E_FAIL The value returned if an internal error occurs. |
| getTypeFromName Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getTypeFromName Method | ParameterspwchUri[in] The namespace URI or, if the namespace has no URI, an empty string.cchUri[in] The length of the namespace URI string.pwchLocalName[in] The local name of the attribute.cchLocalName[in] The length of the local name string.ppwchType[out] The returned type of the attribute. ppwchType should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchType, you should make a deep copy.pcchType[out] The length of the attribute-type string.Return ValuesS_OK The value returned if the attribute type is returned successfully.E_INVALIDARG The value returned if an invalid index or no matching attribute is found.E_FAIL The value returned if an internal error is reported. |
| getURI Method [ISAXAttributes] | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getURI Method [ISAXAttributes] | ParametersnIndex[in] The attribute's index (zero-based).ppwchUri[out] The namespace URI. ppwchUri should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchUri, you should make a deep copy.pcchUri[out] The length of the namespace URI.Return ValuesS_OK The value returned if the URI is returned successfully.E_INVALIDARG The value returned for an invalid index or if no matching attribute is found.E_FAIL The value returned if an internal error occurs. |
| getValue Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getValue Method | ParametersnIndex[in] The attribute index (zero-based).ppwchValue[out] The string value of the attribute. ppwchValue should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchValue, you should make a deep copy.pcchValue[out] The length of the attribute string.Return ValuesIn C++, this method returns a Null value if the index is out of range.S_OK The value returned if the text value is returned successfully.E_INVALIDARG The value returned if an invalid index or no matching attribute is reported.E_FAIL The value returned if an internal error occurs. |
| getValueFromName Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getValueFromName Method | ParameterspwchUri[in] The namespace URI or, if the namespace has no URI, an empty string.cchUri[in] The length of the URI string.pwchLocalName[in] The local name of the attribute.cchLocalName[in] The length of the local name string.ppwchValue[out] The string value of the attribute. ppwchValue should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchValue, you should make a deep copy.pcchValue[out] The length of the attribute's string value.Return ValuesS_OK The value returned if the text value is returned successfully.E_INVALIDARG The value returned for an invalid index or if no matching attribute is reported.E_FAIL The value returned if an internal error occurs. |
| getValueFromQName Method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXAttributes Interface > getValueFromQName Method | ParameterspwchQName[in] The XML 1.0 qualified name.cchQName[in] The length of the qualified name string.pwchValue[out] The string value of the qualified name. ppwchValue should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchValue, you should make a deep copy.pcchValue[out] The length of the qualified name.Return ValuesS_OK The value returned if the text value is returned successfully.E_INVALIDARG The value returned for an invalid index or if no matching attribute is found.E_FAIL The value returned if an internal error occurs. |
| getPublicId Method (C/C++) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXLocator Interface > getPublicId Method (C/C++) | The public identifier or Null (if none is available). ppwchPublicId should not be modified or deleted, because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchPublicId, you should make a deep copy. |
| getSystemId Method (C/C++) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXLocator Interface > getSystemId Method (C/C++) | The system identifier or Null (if none is available). ppwchSystemId should not be modified or deleted because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchSystemId, you should make a deep copy. |
| getBaseURL Method (C/C++) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXXMLReader Interface > getBaseURL Method (C/C++) | The base URL (zero-terminated Unicode string) for the document. ppwchBaseUrl should not be modified or deleted because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchBaseUrl, you should make a deep copy. |
| getSecureBaseURL Method (C/C++) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > MSXML > SAX2 > SAX2 Reference > SAX2 COM/C++ Interfaces > ISAXXMLReader Interface > getSecureBaseURL Method (C/C++) | The secure base URL (zero-terminated Unicode string). ppwchSecureBaseUrl should not be modified or deleted because this can cause undefined behavior in the SAX parser. If you want to preserve the value that was returned in ppwchSecureBaseUrl, you should make a deep copy. |
| Getting Started with the Packaging API | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Programming Guide > Getting Started with the Packaging API | The Packaging APIs do not support any form of marshaling across apartments; if the caller attempts to implement marshaling for Packaging interfaces the attempt will fail or cause undefined behavior. Passing raw pointers to Packaging objects across apartments may lead to undefined behavior. The following operations will result in undefined behavior; errors that occur as a result of these operations may not be recoverable. |
| How to Load a Package for Reading | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Programming Guide > Packages Fundamentals > Packages How-To Topics > How to Load a Package for Reading | Important The stream that you use to load a package for reading remains active for the lifetime of the package object with which it is associated. Do not you use the same stream for both read and write operations because this can cause undefined behavior. |
| How to Save a Package | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Programming Guide > Packages Fundamentals > Packages How-To Topics > How to Save a Package | Important Using the same stream to both deserialize and serialize a package is not recommended and may result in undefined behavior. |
| OPC_STREAM_IO_MODE enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Reference > Packaging Enumerations > OPC_STREAM_IO_MODE | Important Reading and writing to the same package is not recommended and may result in undefined behavior. |
| IOpcFactory interface | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Reference > Packaging Interfaces > Core Packaging Interfaces > IOpcFactory | Do not use a stream to serialize package data when the same stream is being used to deserialize a package; attempting to do so may result in undefined behavior. |
| IOpcFactory::CreateStreamOnFile method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Reference > Packaging Interfaces > Core Packaging Interfaces > IOpcFactory > CreateStreamOnFile | Do not use a stream to serialize package data when the same stream is being used to deserialize a package, because the attempt may result in undefined behavior. |
| IOpcFactory::ReadPackageFromStream method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Reference > Packaging Interfaces > Core Packaging Interfaces > IOpcFactory > ReadPackageFromStream | Do not use a stream to serialize package data when the same stream is being used to deserialize a package, because the attempt may result in undefined behavior. |
| IOpcFactory::WritePackageToStream method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Packaging > Packaging API Reference > Packaging Interfaces > Core Packaging Interfaces > IOpcFactory > WritePackageToStream | Do not use a stream to serialize package data when the same stream is being used to deserialize a package, because the attempt may result in undefined behavior. |
| VDS Enumerations | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Enumerations | This enumeration is reserved for system use. |
| VDS_STORAGE_BUS_TYPE enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Enumerations > VDS_STORAGE_BUS_TYPE | This value is reserved for system use. |
| IVdsOpenVDisk::Compact method | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Interfaces > IVdsOpenVDisk > Compact Method | This parameter is reserved for system use. |
| VDS Structures | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Structures | This structure is reserved for system use. |
| CHANGE_ATTRIBUTES_PARAMETERS structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Structures > CHANGE_ATTRIBUTES_PARAMETERS | such as Disk Defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute. |
| CREATE_PARTITION_PARAMETERS structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Virtual Disk Service > VDS Reference > VDS Structures > CREATE_PARTITION_PARAMETERS | such as Disk Defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute. |
| ADO Error Reference | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft ActiveX Data Objects (ADO) > ADO Programmer's Guide > ActiveX Data Objects (ADO) > Error Handling > ADO Errors > ADO Error Reference | For internal use only. Don't use. (Entry was included for the sake of completeness. This error should not appear in your code.) For internal use only. Don't use. (Entry included for the sake of completeness. This error should not appear in your code.) |
| ErrorValueEnum | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft ActiveX Data Objects (ADO) > ADO Programmer's Reference > ADO API Reference > ADO Enumerated Constants > ErrorValueEnum | For internal use only. Do not use. For internal use only. Do not use. |
| SQLSetDescField Function | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft Open Database Connectivity (ODBC) > ODBC Programmer's Reference > API Reference > ODBC API Reference > SQLSetDescField Function | Driver behavior is undefined if the application sets the elements of the row status array pointed to by the SQL_DESC_ARRAY_STATUS_PTR field of the IRD. |
| Asynchronous Execution (Notification Method) | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft Open Database Connectivity (ODBC) > ODBC Programmer's Reference > Developing Applications > Executing Statements ODBC > Asynchronous Execution > Asynchronous Execution (Notification Method) | An application should check the Driver Manager version before using this feature. Otherwise, if a poorly written driver does not error out and the Driver Manager version is pre ODBC 3.81, behavior is undefined. |
| Allocating and Freeing Buffers | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft Open Database Connectivity (ODBC) > ODBC Programmer's Reference > Developing Applications > ODBC Fundamentals > Buffers > Allocating and Freeing Buffers | // *ValuePtr. Because ValuePtr has been freed, the behavior is undefined |
| Appendix B: ODBC State Transition Tables | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Data Access Components > Microsoft Open Database Connectivity (ODBC) > ODBC Programmer's Reference > ODBC Appendixes > Appendix B: ODBC State Transition Tables | (IH) — An invalid handle was passed to the function. If the handle was a null handle or was a valid handle of the wrong type — for example, a connection handle was passed when a statement handle was required — the function returns SQL_INVALID_HANDLE; otherwise the behavior is undefined and probably fatal. This error is shown only when it is the only possible outcome of calling the function in the specified state. This error does not change the state and is always detected by the Driver Manager, as indicated by the parentheses. |
| Storage Management API Classes | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes | This class is reserved for system use. Do not use. |
| MSFT_Disk class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_Disk | This value is reserved for system use. |
| MSFT_Partition class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_Partition | If TRUE, the partition is not detected by the mount manager. As a result, the partition does not receive a drive letter, does not receive a volume GUID path, does not host volume mount points, and is not enumerated by calls to FindFirstVolume and FindNextVolume. This ensures that applications such as Disk Defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute on its shadow copies. This value is reserved for system use. |
| SetAttributes method of the MSFT_Partition class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_Partition > SetAttributes method | TRUE if the partition is not detected by the mount manager. As a result, the partition does not receive a drive letter, does not receive a volume GUID path, does not host volume mount points, and is not enumerated by calls to FindFirstVolume and FindNextVolume. This ensures that applications such as disk defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute on its shadow copies. |
| MSFT_PhysicalDisk class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_PhysicalDisk | This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. |
| MSFT_StorageEvent class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_StorageEvent | This value is reserved for system use. |
| MSFT_StorageJob class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_StorageJob | This value is reserved for system use. |
| MSFT_StoragePool class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_StoragePool | This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. |
| MSFT_StorageSubSystem class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_StorageSubSystem | This value is reserved for system use. Reserved for system use. Reserved for system use. |
| MSFT_VirtualDisk class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_VirtualDisk | This value is reserved for system use. |
| MSFT_VirtualDiskToVirtualDisk class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > Windows Storage Management API > Storage Management API Classes > MSFT_VirtualDiskToVirtualDisk | This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. This value is reserved for system use. |
| ISCSI_LOGIN_OPTIONS structure | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > iSCSI Discovery Library API > iSCSI Discovery Library Reference > iSCSI Discovery Library Structures > ISCSI_LOGIN_OPTIONS | Reserved for internal use. |
| WT_Disk class | Dev Center - Desktop > Docs > Windows Development Reference > Data Access and Storage > iSCSI Software Target API > iSCSI Software Target Reference > WT_Disk | Reserved for system use. Reserved for system use. Reserved for system use. |
| Function Discovery Categories | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Function Discovery > About Function Discovery > Function Discovery Categories | Provider categories contain Function Discovery providers, and are used by the Function Discovery runtime to determine which discovery providers to load. The category name begins with the string "Provider\". Client programs usually do not access or search on provider categories with the possible exception of system utility and test applications. |
| Using Logical and Physical Addresses | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Web Services on Devices > Using Web Services on Devices > WSD Device Development > WSD Device Implementation Recommendations > Using Logical and Physical Addresses | If logical addresses are used, then there are some scenarios where the implementation behavior is undefined. The WS-Discovery specification does not describe what it means for a service to reside at a logical address. R1001 of the WS-Discovery specification recommends against using WS-Discovery on hosted services because of the associated network chatter. |
| IWSDUdpAddress interface | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Web Services on Devices > Web Services on Devices Reference > Web Services on Devices Interfaces > IWSDUdpAddress | Gets the alias for the discovery address. This method is reserved for internal use and should not be called. Sets the alias for the discovery address. This method is reserved for internal use and should not be called. |
| WIA Event Identifiers | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Windows Image Acquisition (WIA) > WIA > Reference > WIA Application Programming Interface > Constants > WIA Event Identifiers | WIA_EVENT_STI_PROXYIntended for internal use only. Do not use. |
| IWiaDataCallback::BandedDataCallback method | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Windows Image Acquisition (WIA) > WIA > Reference > WIA Application Programming Interface > Interfaces > IWiaDataCallback > BandedDataCallback | Reserved for internal use by the WIA run-time system. Reserved for internal use by the WIA run-time system. |
| Security Considerations: Windows Image Acquisition | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Windows Image Acquisition (WIA) > WIA > Security Considerations: Windows Image Acquisition | WIA uses several directories and registry keys internally to store data or information. Do not access these directories or registry keys directly. Instead, use the exposed interface methods to specify directories for acquired images. |
| Security Considerations: Windows Image Acquisition Automation Layer | Dev Center - Desktop > Docs > Windows Development Reference > Devices > Windows Image Acquisition (WIA) > WIA Automation > Overviews/Tutorials > Security Considerations: Windows Image Acquisition Automation Layer | Windows Image Acquisition (WIA) uses several directories and registry keys internally to store data or information. Do not access these directories or registry keys directly. Instead, use the exposed methods to specify directories for acquired images. |
| SymSearch function | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Debugging and Error Handling > Debug Help Library > DbgHelp Reference > DbgHelp Functions > SymSearch | For internal use only. |
| IMAGEHLP_STACK_FRAME structure | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Debugging and Error Handling > Debug Help Library > DbgHelp Reference > DbgHelp Structures > IMAGEHLP_STACK_FRAME | This member is reserved for system use. This member is reserved for system use. |
| SYMBOL_INFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Debugging and Error Handling > Debug Help Library > DbgHelp Reference > DbgHelp Structures > SYMBOL_INFO | This member is reserved for system use. |
| Getting Notifications | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Debugging and Error Handling > Debug Help Library > Using DbgHelp > Getting Notifications | After calling SymInitialize, use SymRegisterCallback64 to register a callback function that DbgHelp will call whenever an interesting event occurs. In this example, the callback function is called SymRegisterCallbackProc64. Symbol callback functions are passed an assortment of action codes that they can handle according to type. In this example, we are handling only the CBA_EVENT action code. This function passes a string containing verbose information about an event that occurred in the process of loading a symbol. This event could be anything from an attempt to read the data within an executable image to the successful location of a symbol file. SymRegisterCallbackProc64 displays that string and returns TRUE. Important Make sure you return FALSE to every action code that you do not handle, otherwise you may experience undefined behavior. Refer to SymRegisterCallbackProc64 for a list of all the action codes and their implications. |
| GetEnabledXStateFeatures function | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Debugging and Error Handling > Intel AVX > AVX Functions > GetEnabledXStateFeatures | An application should call this function to determine what features are present and enabled on the system before using an XState processor feature or attempting to manipulate XState contexts. Bits 0 and 1 refer to the X87 FPU and the presence of SSE registers, respectively. The meanings of specific feature bits beyond 0 and 1 are defined in the Programmer Reference Manuals released by the processor vendors.Note Not all features supported by a processor may be enabled on the system. Using a feature which is not enabled may result in exceptions or undefined behavior. |
| DisplayToID | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Performance Counters > Performance Counters Reference > SQL Log File Schema > DisplayToID | RunID: Reserved for internal use. |
| ReportFault function | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Error Reporting > WER Reference > WER Functions > ReportFault | This parameter is reserved for system use and should be set to zero. |
| Event Sources | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Logging > About Event Logging > Event Logging Elements > Event Sources | Security log is for system use only. Device drivers should add their names to the |
| Message Text Files | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Logging > About Event Logging > Event Logging Elements > Message Files > Message Text Files | FacilityNames=(name=number[:name])Set of names that are allowed for the facility values in a message definition. Associated with each facility name is a number that, when shifted left by 16 bits, gives the bit pattern to logical-OR with the severity and message ID values to form the message code. Any severity value that does not fit in 12 bits is an error. This allows for 4096 facility codes; the first 256 codes are reserved for system use. The facility codes can be given symbolic names as well.The default value is defined as follows: FacilityNames=( System=0x0FF Application=0xFFF) |
| RegisterEventSource function | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Logging > Event Logging Reference > Event Logging Functions > RegisterEventSource | However, the Security log is for system use only. |
| Logging Mode Constants | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Tracing > Event Tracing Reference > Event Tracing Constants > Logging Mode Constants | EVENT_TRACE_HEADER. Note This mode should not be used. It is reserved for internal use. |
| ControlCallback callback function | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Tracing > Event Tracing Reference > Event Tracing Functions > ControlCallback | Reserved for internal use. |
| WNODE_HEADER structure | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Event Tracing > Event Tracing Reference > Event Tracing Structures > WNODE_HEADER | Reserved for internal use. Reserved for internal use. Reserved for internal use. Reserved for internal use. |
| OpcodeType Complex Type | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Windows Event Log > Windows Event Log Reference > EventManifest Schema > EventManifest Schema Complex Types > OpcodeType Complex Type | Reserved for internal use only. |
| ProviderType Complex Type | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Windows Event Log > Windows Event Log Reference > EventManifest Schema > EventManifest Schema Complex Types > ProviderType Complex Type | For internal use only. For internal use only. |
| EVT_EVENT_METADATA_PROPERTY_ID enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Events > Windows Event Log > Windows Event Log Reference > Windows Event Log Enumerations > EVT_EVENT_METADATA_PROPERTY_ID | Identifies the keyword attribute of the event definition. The variant type for this property is EvtVarTypeUInt64. This property does not contain the list of keyword names that you specified in the event definition but instead contains a 64-bitmask of all the keywords. The top 16 bits of the mask are reserved for internal use and should be ignored when determining the keyword bits that the event definition set. |
| The Butterfly View | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Performance Analyzer (WPA) > Performance Analysis Whitepapers > Exploring Process Heaps Using Windows Performance Analyzer > Analyzing Process Heap Data > Process Heap Summary Tables > The Butterfly View | The following screen shot shows a Butterfly view of heap handle 0x 01de 0000.In this table, Butterfly view of heap handle 0x 01de 0000, a butterfly view is opened using the ntdll.dll!RtlAllocateHeap function as the outermost caller in the 0x01de 000 heap. 164 allocations using 916,929 bytes have been made by GdiPlus.dll. Applications based on the Microsoft Win32 API do not access graphics hardware directly. Instead, GDI+ interacts with device drivers on behalf of applications. |
| ReadyBoot Analysis | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Performance Analyzer (WPA) > Performance Analysis Whitepapers > ReadyBoot Analysis | ReadyBoot analysis is a core piece of a comprehensive boot performance analysis. Read requests that are satisfied from the ReadyBoot RAM cache are not reflected as disk reads in the Disk I/O graphs and summary tables because those reads do not access the disk. In order to develop a complete picture of the I/O activities performed at boot time, one must consider the I/O information presented in the ReadyBoot graphs and summary tables in addition to the I/O information presented in the Disk I/O graphs and summary tables. |
| Stack Walking | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Performance Analyzer (WPA) > Quick Start Guide: WPA Basics > Stack Walking | The following screen shot shows how a butterfly view is opened using ntdll.dll!RtlAllocateHeap function as the outermost caller in the 0x01de 000 heap. 164 allocations using 916,929 bytes have been made by GdiPlus.dll. Applications based on the Microsoft Win32 API do not access graphics hardware directly. Instead, GDI+ interacts with device drivers on behalf of applications. By changing the sorting order to count, as illustrated in the following screen shot, the outermost caller and the expanded the call stacks are displayed. Note the sort is now by the count of allocations. This view presents functions that have the most allocations based on count. |
| Choice Complex Type | Dev Center - Desktop > Docs > Windows Development Reference > Diagnostics > Windows Troubleshooting Platform > WTP Reference > Troubleshooting Schemas > Package Schema > Package Complex Types > Choice Complex Type | ExtensionDescriptionDefaultSpecifies the default selection for a single-response interaction or default selections for a multiple-response interaction. If you specify a default choice for more than one choice in a single-response interaction, the behavior is undefined. The default has no effect if you also specify the CommandLinks extension point.The Default element has no content.IconAn icon to display next to the choice. If you specify the CommandLinks extension point, the icon replaces the green arrow icon. The Icon element contains the resource identifier for the icon (for example, "@resource.dll,-123").RTFDescriptionA rich text format string that replaces the Description element of DisplayInformation. If the client does not support rich text, the description string is used.The RTF string can contain substitution strings (for example, %param%) that are specified in the ContextParameters element of the single-response or multiple-response interaction.The RTFDescription element can contain an RTF string or a localized resource string (for example, "@diag.dll,-123" or "@diag.dll,RESOURCE.RTF"). |
| DOC_INFO_2 structure | Dev Center - Desktop > Docs > Windows Development Reference > Documents and Printing > Printing > Print Spooler API > Print Spooler API Reference > Print Spooler API Structures > DOC_INFO_2 | Reserved for internal use; should be zero. |
| Accessing an Alternate Registry View | Dev Center - Desktop > Docs > Windows Development Reference > Getting Started > Programming Guide for 64-bit Windows > Running 32-bit Applications > Registry Redirector > Accessing an Alternate Registry View | Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP: If both flags are specified, the function’s behavior is undefined. |
| Remoting Changes | Dev Center - Desktop > Docs > Windows Development Reference > Getting Started > Windows Vista > Windows Vista Developer Story > Communication > Connecting Technologies > .NET Framework Communication > .NET Framework Remoting Changes | The following tables list the new .NET Framework remoting namespaces and types. Enumerations and types meant for internal use only are not listed. Only one new namespace has been added to the .NET Framework class library to support IPC channels. |
| DCompositionCreateSurfaceHandle function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectComposition > DirectComposition reference > Functions > DCompositionCreateSurfaceHandle | Read access. For internal use only. Write access. For internal use only. |
| IDCompositionSurface::BeginDraw method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectComposition > DirectComposition reference > Interfaces > IDCompositionSurface > BeginDraw method | The retrieved surface rectangle does not contain the previous contents of the bitmap. The application must update every pixel in the update rectangle, either by first clearing the render target, or by issuing enough rendering primitives to fully cover the update rectangle. Because the initial contents of the update surface are undefined, failing to update every pixel leads to undefined behavior. |
| Multiple-element Textures (Direct3D 9) | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Programming Guide for Direct3D 9 > Advanced Topics > Pixel Pipeline > Multiple-element Textures | SetSamplerState is called to set D3DSAMP_ELEMENTINDEX to the appropriate element number in the multiple-element texture from which the sampler samples. Default value for this state is 0, which means non-multiple-element textures will work. Setting this state to an inappropriate number results in an undefined behavior - if the multiple-element texture is only two elements wide but the sampler is asked to sample from the fourth element, for example. |
| Math Function Support in D3DX (Direct3D 9) | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Programming Guide for Direct3D 9 > Getting Started > D3DX > Math Function Support in D3DX | When using the FLOAT16 data type, be sure to limit values to a maximum of D3DX_16F_MAX. Any FLOAT16 value that exceeds this will result in undefined behavior in the pipeline. See Other D3DX Constants. |
| Device Types (Direct3D 9) | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Programming Guide for Direct3D 9 > Getting Started > Direct3D Devices > Device Types | Applications do not access graphics adapters directly. They call Direct3D functions and methods. Direct3D accesses the hardware through the hal. If the computer that your application is running on supports the hal, it will gain the best performance by using a hal device. |
| Texture Blending Operations and Arguments (Direct3D 9) | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Programming Guide for Direct3D 9 > Getting Started > Direct3D Textures > Texture Blending > Texture Blending Operations and Arguments | Note You can disable a texture stage - and any subsequent texture blending stages in the cascade - by setting the color operation for that stage to D3DTOP_DISABLE. Disabling the color operation effectively disables the alpha operation as well. Alpha operations cannot be disabled when color operations are enabled. Setting the alpha operation to D3DTOP_DISABLE when color blending is enabled causes undefined behavior. |
| Troubleshooting (Direct3D 9) | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Programming Guide for Direct3D 9 > Programming Tips > Troubleshooting | Although several Direct3D Immediate Mode methods impose limits on the values that they can accept, these limits are often only checked and enforced by the debug version of the Direct3D Immediate Mode run time. Applications must conform to these limits, or unpredictable and undesirable results can occur when running on the retail version of Direct3D. For example, the IDirect3DDevice9::DrawPrimitive method accepts a parameter (PrimitiveCount) that indicates the number of primitives that the method will render. The method can only accept values between 0 and D3DMAXNUMPRIMITIVES. In the debug version of Direct3D, if you pass more than D3DMAXNUMPRIMITIVES primitives, the method fails gracefully, printing an error message to the error log, and returning an error value to your application. Conversely, if your application makes the same error when it is running with the retail version of the run time, behavior is undefined. For performance reasons, the method does not validate the parameters, resulting in unpredictable and completely situational behavior when they are not valid. In some cases the call might work, and in other cases it might cause a memory fault in Direct3D. If an invalid call consistently works with a particular hardware configuration and DirectX version, there is no guarantee that it will continue to function on other hardware or with later releases of DirectX. |
| D3DCREATE | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Reference for Direct3D 9 > Direct3D Reference > Direct3D Constants > D3DCREATE | Portions of Direct3D assume floating-point unit exceptions are masked; unmasking these exceptions may result in undefined behavior. |
| D3DTEXTUREOP enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Direct3D 9 Graphics > Reference for Direct3D 9 > Direct3D Reference > Direct3D Enumerations > D3DTEXTUREOP | Disables output from this texture stage and all stages with a higher index. To disable texture mapping, set this as the color operation for the first texture stage (stage 0). Alpha operations cannot be disabled when color operations are enabled. Setting the alpha operation to D3DTOP_DISABLE when color blending is enabled causes undefined behavior. |
| Tips and Tricks Using Managed Code | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > DirectX 9.0 for Managed Code > Introducing DirectX 9.0 > Tips and Tricks Using Managed Code | DirectX 9.0 for Managed Code does not support class inheritance in applications. Inheriting from DirectX 9.0 for Managed Code classes is not recommended and the resulting behavior is undefined. |
| TextureOperation Enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > DirectX 9.0 for Managed Code > Namespaces > Microsoft.DirectX.Direct3D > Enumerations > TextureOperation | Disable1Disables output from the texture stage and all stages with a higher index. To disable texture mapping, set this flag as the color operation for the first texture stage (stage 0). Alpha operations cannot be disabled when color operations are enabled. Setting the alpha operation to Disable when color blending is enabled causes undefined behavior. |
| Lockless Programming Considerations for Xbox 360 and Microsoft Windows | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Classic DirectX Graphics > Technical Articles > Lockless Programming Considerations for Xbox 360 and Microsoft Windows | // This is not atomic and gives undefined behavior |
| DXGI_USAGE | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > DXGI > DXGI Reference > DXGI Constants > DXGI_USAGE | This flag is for internal use only. |
| D3D11_1_CREATE_DEVICE_CONTEXT_STATE_FLAG enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Direct3D 11 Reference > Direct3D 11 Reference > Core Reference > Core Enumerations > D3D11_1_CREATE_DEVICE_CONTEXT_STATE_FLAG | By using this flag, you can increase performance. However, if you use this flag and your application calls methods from multiple threads, undefined behavior might result. |
| D3D11_CREATE_DEVICE_FLAG enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Direct3D 11 Reference > Direct3D 11 Reference > Core Reference > Core Enumerations > D3D11_CREATE_DEVICE_FLAG | By using this flag, you can increase performance. However, if you use this flag and your application calls methods of Direct3D 11 interfaces from multiple threads, undefined behavior might result. |
| ID3D11Device::CreateInputLayout method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Direct3D 11 Reference > Direct3D 11 Reference > Core Reference > Core Interfaces > ID3D11Device > CreateInputLayout | What are the consequences of this? Will it merely result in inefficiencies (eg. vertex elements to be processed needlessly only to be ignored by the vertex shader). Or is it undefined behavior that just happens to be tolerated by my video card's driver? |
| ID3D11DeviceContext::CopySubresourceRegion method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Direct3D 11 Reference > Direct3D 11 Reference > Core Reference > Core Interfaces > ID3D11DeviceContext > CopySubresourceRegion | The source box must be within the size of the source resource. The destination offsets, (x, y, and z) allow the source box to be offset when writing into the destination resource; however, the dimensions of the source box and the offsets must be within the size of the resource. If you try and copy outside the destination resource or specify a source box that is larger than the source resource, the behavior of CopySubresourceRegion is undefined. If you created a device that supports the debug layer, the debug output reports an error on this invalid CopySubresourceRegion call. Invalid parameters to CopySubresourceRegion cause undefined behavior and might result in incorrect rendering, clipping, no copy, or even the removal of the rendering device. |
| D3D11_RASTERIZER_DESC1 structure | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Direct3D 11 Reference > Direct3D 11 Reference > Core Reference > Core Structures > D3D11_RASTERIZER_DESC1 | Otherwise, rendering behavior is undefined. For info about how to configure depth-stencil, see Configuring Depth-Stencil Functionality. |
| New Resource Types | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Programming Guide for Direct3D 11 > Graphics Pipeline > Compute Shader Overview > New Resource Types | A byte address buffer is a buffer whose contents are addressable by a byte offset. Normally, the contents of a buffer are indexed per element using a stride for each element (S) and the element number (N) as given by S*N. A byte address buffer, which can also be called a raw buffer, uses a byte value offset from the beginning of the buffer to access data. The byte value must be a multiple of four so that it is DWORD aligned. If any other value is provided, behavior is undefined. |
| Tessellation Overview | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Programming Guide for Direct3D 11 > Graphics Pipeline > Tessellation Overview | After the domain shader completes, tessellation is finished and pipeline data continues to the next pipeline stage (geometry shader, pixel shader etc). A geometry shader that expects primitives with adjacency (for example, 6 vertices per triangle) is not valid when tessellation is active (this results in undefined behavior, which the debug layer will complain about). |
| Direct3D 11.1 Features | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > Direct3D 11 Graphics > Programming Guide for Direct3D 11 > Introduction > Direct3D 11.1 Features | Otherwise, rendering behavior is undefined. For info about how to configure depth-stencil, see Configuring Depth-Stencil Functionality. |
| Semantics | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > HLSL > Reference for HLSL > Language Syntax > Semantics | When using dynamic-flow control, it is impossible to determine at compile time whether a shader that writes SV_Depth in some paths will be guaranteed to write SV_Depth in every execution. Failure to write SV_Depth when declared results in undefined behavior (which may or may not include discard of the pixel). |
| Shader Constants | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > Direct3D > HLSL > Reference for HLSL > Shader Models vs Shader Profiles > Shader Model 4 > Shader Constants (DirectX HLSL) | per pipeline stage (2 additional slots are reserved for internal use). |
| XAudio2 Error Codes | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > XAudio2 APIs > Programming Reference > Constants > XAudio2 Error Codes | in debug builds and undefined behavior in retail builds, so no error code is defined for them.) |
| IXAudio2::Release method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > DirectX Graphics and Gaming > XAudio2 APIs > Programming Reference > Interfaces > IXAudio2 > Release method | When the final Release is called on a given XAudio2 object, all voice objects that are associated with it are destroyed. Any pointers to these objects that are still held by the client become invalid immediately. Any calls that are made to them cause undefined behavior. The audio processing engine is also stopped. This is so that after Release is returned, the client can safely free any data that is referenced by the graph (for example, audio source buffers or callback handling objects). |
| Bitmap.GetHistogram method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > GDI+ > GDI+ Reference > Classes > Bitmap > Bitmap Methods > GetHistogram | It uses delete ch0; whereas the correct C++ form is delete [] ch0;Deleting an array without the [] can lead to undefined behavior (as I understand things). |
| LinearGradientBrush.SetBlend method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > GDI+ > GDI+ Reference > Classes > LinearGradientBrush > LinearGradientBrush Methods > SetBlend | Pointer to an array of real numbers that specify blend positions. Each number in the array indicates a percentage of the distance between the starting boundary and the ending boundary and is in the range from 0.0 through 1.0, where 0.0 indicates the starting boundary of the gradient and 1.0 indicates the ending boundary. There must be at least two positions specified: the first position, which is always 0.0f, and the last position, which is always 1.0f. Otherwise, the behavior is undefined. A blend position between 0.0 and 1.0 indicates a line, parallel to the boundary lines, that is a certain fraction of the distance from the starting boundary to the ending boundary. For example, a blend position of 0.7 indicates the line that is 70 percent of the distance from the starting boundary to the ending boundary. The color is constant on lines that are parallel to the boundary lines. |
| LinearGradientBrush.SetInterpolationColors method | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > GDI+ > GDI+ Reference > Classes > LinearGradientBrush > LinearGradientBrush Methods > SetInterpolationColors | Pointer to an array of real numbers that specify the blend positions. Each number in the array specifies a percentage of the distance between the starting boundary and the ending boundary and is in the range from 0.0 through 1.0, where 0.0 indicates the starting boundary of the gradient and 1.0 indicates the ending boundary. There must be at least two positions specified: the first position, which is always 0.0f, and the last position, which is always 1.0f. Otherwise, the behavior is undefined. A blend position between 0.0 and 1.0 indicates the line, parallel to the boundary lines, that is a certain fraction of the distance from the starting boundary to the ending boundary. For example, a blend position of 0.7 indicates the line that is 70 percent of the distance from the starting boundary to the ending boundary. The color is constant on lines that are parallel to the boundary lines. |
| glDisableClientState function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glDisableClientState | Calling glEnableClientState and glDisableClientState between calls to glBegin and the corresponding call to glEnd can cause an error. If no error is generated, the behavior is undefined. |
| glEnableClientState function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glEnableClientState | Calling glEnableClientState and glDisableClientState between calls to glBegin and the corresponding call to glEnd can cause an error. If no error is generated, the behavior is undefined. |
| glVertex2d function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex2d | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex2f function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex2f | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex2i function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex2i | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex2s function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex2s | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex3d function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex3d | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex3f function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex3f | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex3i function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex3i | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex3s function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex3s | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex4d function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex4d | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex4f function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex4f | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex4i function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex4i | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| glVertex4s function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > OpenGL > OpenGL Reference > GL Functions > glVertex Functions > glVertex4s | Invoking glVertex outside of a glBegin/glEnd pair results in undefined behavior. |
| ENUMTYPE Structure | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > Windows Color System > Reference > Structures > ENUMTYPE | Reserved for internal use. |
| PROFILEHEADER Structure | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > Windows Color System > Reference > Structures > PROFILEHEADER | Reserved for internal use. |
| Windows GDI | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > Windows GDI | The Microsoft Windows graphics device interface (GDI) enables applications to use graphics and formatted text on both the video display and the printer. Windows-based applications do not access the graphics hardware directly. Instead, GDI interacts with device drivers on behalf of applications. |
| ExtTextOut function | Dev Center - Desktop > Docs > Windows Development Reference > Graphics and Gaming > Legacy Graphics > Windows GDI > Fonts and Text > Font and Text Reference > Font and Text Functions > ExtTextOut | Reserved for system use. If an application sets this flag, it loses international scripting support and in some cases it may display no text at all. |
| Option Flags | Dev Center - Desktop > Docs > Windows Development Reference > Internet > Windows HTTP Services (WinHTTP) > WinHTTP Reference > WinHTTP C/C++ API Reference > WinHTTP Constants > Option Flags | This option is reserved for internal use and should not be called. |
| WSDL and Service Contracts | Dev Center - Desktop > Docs > Windows Development Reference > Internet > Windows Web Services > About Windows Web Services > WsUtil Compiler tool > WSDL support | and the wrapper structure contains all of the elements in all of the parts as fields. The wrapper element is for internal use only and it will not be serialized |
| WS_MESSAGE_PROPERTY_ID enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Internet > Windows Web Services > Windows Web Services Reference > Windows Web Services Enumerations > WS_MESSAGE_PROPERTY_ID | on the heap. This will result in undefined behavior. Using the heap of an empty message will result in undefined behavior. |
| DisableMediaSense function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > IP Helper > IP Helper Reference > IP Helper Functions > DisableMediaSense | An application should not use the value pointed to by this variable. This handle is for internal use and should not be closed. |
| ICMP_ECHO_REPLY structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > IP Helper > IP Helper Reference > IP Helper Structures > ICMP_ECHO_REPLY | Reserved for system use. |
| ICMP_ECHO_REPLY32 structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > IP Helper > IP Helper Reference > IP Helper Structures > ICMP_ECHO_REPLY32 | Reserved for system use. |
| NL_INTERFACE_OFFLOAD_ROD structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Management Information Base > Management Information Base Reference > MIB Structures > NL_INTERFACE_OFFLOAD_ROD | Reserved for internal use. Reserved for internal use. |
| Applications | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Message Queuing (MSMQ) > About Message Queuing > Applications | Direct routing versus store-and-forward routing. Direct messages are sent directly to the computer where the destination queue resides and do not access the directory service. Store-and-forward routing requires a connection to the directory service, and the path that the message takes is determined by Message Queuing. |
| PEER_GROUP_PROPERTIES structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Peer-to-Peer > Peer Infrastructure > Grouping API > Grouping API Reference > Grouping API Structures > PEER_GROUP_PROPERTIES | Specifies the lifetime, in seconds, of presence information published to a peer group. The default value is 300 seconds. Do not set the value of ulPresenceLifetime to less than 300 seconds. If this member is set to less than the 300–second default value, then undefined behavior can occur. |
| RPC NDR Engine | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine | Although stubs are C code that are generated by MIDL, applications are advised to treat stubs as opaque, and strongly discouraged from modifying anything inside the stub. The behavior is undefined if these NDR routines are called out of context. |
| Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrClearOutParameters | Pointer to MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The structure is for internal use only and should not be modified. | |
| Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrConformantArrayUnmarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. This structure is for internal use only and should not be modified. | |
| NdrConformantStringBufferSize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrConformantStringBufferSize | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The BufferLength member contains the size of the buffer. Structure is for internal use only; do not modify. |
| NdrConformantStringMarshall function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrConformantStringMarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. This structure is for internal use only and should not be modified. |
| NdrConformantStringUnmarshall function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrConformantStringUnmarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. This structure is for internal use only and should not be modified. |
| NdrContextHandleInitialize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrContextHandleInitialize | Pointer to a MIDL_STUB_MESSAGE structure that contains the current status of the RPC stub. Structure is for internal use only; do not modify. |
| NdrContextHandleSize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrContextHandleSize | Pointer to a MIDL_STUB_MESSAGE structure that contains the current status of the RPC stub. The BufferLength member contains the size of the context handle, in bytes. Structure is for internal use only; do not modify. |
| Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrConvert | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The pRpcMsg member points to a structure whose Buffer member contains the data to convert. This structure is for internal use only and should not be modified. | |
| NdrInterfacePointerBufferSize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrInterfacePointerBufferSize | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The BufferLength member contains the size of the buffer. This structure is for internal use only and should not be modified. |
| NdrInterfacePointerMarshall function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrInterfacePointerMarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. This structure is for internal use only and should not be modified. |
| NdrPointerBufferSize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrPointerBufferSize | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The BufferLength member contains the size of the buffer. This structure is for internal use only and should not be modified. |
| NdrPointerFree function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrPointerFree | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. This structure is for internal use only and should not be modified. |
| NdrPointerUnmarshall function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrPointerUnmarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. Structure is for internal use only; do not modify. |
| NdrProxyFreeBuffer function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrProxyFreeBuffer | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The pRpcMsg member points to a structure whose Buffer member is to be freed. Structure is for internal use only; do not modify. |
| NdrProxyGetBuffer function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrProxyGetBuffer | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. The pRpcMsg member points to a structure whose Buffer member points to the newly allocated buffer. Structure is for internal use only; do not modify. |
| NdrProxyInitialize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrProxyInitialize | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. Structure is for internal use only; do not modify. Pointer to a MIDL_STUB_DESC structure that contains a descriptor for the RPC stub. Structure is for internal use only; do not modify. |
| NdrProxySendReceive function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrProxySendReceive | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. Structure is for internal use only; do not modify. |
| NdrSimpleTypeMarshall function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrSimpleTypeMarshall | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. Structure is for internal use only; do not modify. |
| NdrStubInitialize function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Remote Procedure Call (RPC) > RPC NDR Engine > RPC NDR Interface Reference > NdrStubInitialize | Pointer to a MIDL_STUB_MESSAGE structure that maintains the current status of the RPC stub. Structure is for internal use only; do not modify. Pointer to a MIDL_STUB_DESC structure that contains a descriptor for the RPC stub. Structure is for internal use only; do not modify. |
| RasCustomDialDlg callback function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Routing and Remote Access Service > Remote Access > Remote Access Service > Remote Access Service Reference > Remote Access Service Functions > RasCustomDialDlg | Reserved for internal use. This parameter will always be NULL. |
| RASENTRY structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Routing and Remote Access Service > Remote Access > Remote Access Service > Remote Access Service Reference > Remote Access Service Structures > RASENTRY | RASET_InternetConnection Manager (CM) connection. This value is reserved for system use. |
| MSFT_SmbShare class | Dev Center - Desktop > Docs > Windows Development Reference > Networking > SMB Management API > MSFT_SmbShare | This method is reserved for system use. |
| Initiate a Session | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Telephony Application Programming Interfaces > Microsoft Telephony Overview > TAPI Applications > Session Control > Session Operations > Initiate a Session | Toll lists are not relevant to service providers, or to applications that do not access a telephone network. |
| lineInitializeEx function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Telephony Application Programming Interfaces > TAPI 2.2 > TAPI 2.2 Reference > TAPI Functions > Line Device Functions > lineInitializeEx | CloseHandle, and so on) or undefined behavior results; the application can only wait on this event using functions such as |
| phoneInitializeEx function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Telephony Application Programming Interfaces > TAPI 2.2 > TAPI 2.2 Reference > TAPI Functions > Phone Device Functions > phoneInitializeEx | CloseHandle, and so on) or undefined behavior results; the application can only wait on this event using functions such as |
| FwpmFreeMemory0 function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Functions > Shared Functions > FwpmFreeMemory0 | If the caller passes a pointer that is not valid, the behavior is undefined. |
| Filtering Condition Identifiers | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Constants > Filtering Conditions > Filtering Condition Identifiers | Reserved for internal use. Reserved for internal use. The interface IPv6 scope identifier. Reserved for internal use. Reserved for internal use. Reserved for internal use. Reserved for internal use. The following filtering conditions are included in Windows Server 2008 R2 and Windows 7, but are reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. Reserved for system use. |
| FWPM_FILTER0 structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Structures > Management Structures > FWPM_FILTER0 | Reserved for system use. |
| FWPM_NET_EVENT_CLASSIFY_DROP_MAC0 structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Structures > Management Structures > FWPM_NET_EVENT_CLASSIFY_DROP_MAC0 | Reserved for internal use. |
| FWPM_NET_EVENT_ENUM_TEMPLATE0 structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Structures > Management Structures > FWPM_NET_EVENT_ENUM_TEMPLATE0 | The interface IPv6 scope identifier. Reserved for internal use. |
| FWPM_NET_EVENT_HEADER1 structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Filtering Platform > Windows Filtering Platform API Reference > WFP Structures > Management Structures > FWPM_NET_EVENT_HEADER1 | Note FWPM_NET_EVENT_HEADER1 is a specific implementation of FWPM_NET_EVENT_HEADER that is reserved for system use. For Windows Vista and Windows 7, FWPM_NET_EVENT_HEADER0 is available. For Windows 8 Release Preview, FWPM_NET_EVENT_HEADER2 is available. This structure is reserved for system use. FWPM_NET_EVENT_HEADER0 or FWPM_NET_EVENT_HEADER2 should be used in place of FWPM_NET_EVENT_HEADER1. |
| Overlapped I/O and Event Objects | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > About Winsock > Overlapped I/O and Event Objects | In many cases, Winsock overlapped operations using AcceptEx, ConnectEx, WSASend, WSARecv, TransmitFile, and similar functions are cancelable. However, behavior is undefined for the continued use of a socket that has canceled outstanding operations. The closesocket function should be called after canceling an overlapped operation. Therefore, for best results, instead of canceling the I/O directly, the closesocket function should be called to close the socket which will eventually discontinue all pending operations. |
| SOL_SOCKET Socket Options | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Socket Options > SOL_SOCKET Socket Options | SO_REUSEADDRyesyesDWORD (boolean)Allows socket to bind to an address and port already in use. The SO_EXCLUSIVEADDRUSE option can prevent this. Also, if two sockets are bound to the same port the behavior is undefined as to which port will receive packets. |
| SO_EXCLUSIVEADDRUSE socket option | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Socket Options > SOL_SOCKET Socket Options > SO_EXCLUSIVEADDRUSE | * The behavior is undefined as to which socket will receive packets. |
| WSAAccept function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAAccept | Note When issuing a blocking Winsock call such as WSAAccept, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAConnect function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAConnect | Note When issuing a blocking Winsock call such as WSAConnect, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAConnectByList function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAConnectByList | Note When issuing a blocking Winsock call such as WSAConnectByList with the timeout parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAConnectByName function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAConnectByName | Note When issuing a blocking Winsock call such as WSAConnectByName with the timeout parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAJoinLeaf function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAJoinLeaf | Note When issuing a blocking Winsock call such as WSAJoinLeaf, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAPoll function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSAPoll | Note When issuing a blocking Winsock call such as WSAPoll with the timeout parameter set to a negative number, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSARecv function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSARecv | Note When issuing a blocking Winsock call such as WSARecv with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSARecvDisconnect function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSARecvDisconnect | Note When issuing a blocking Winsock call such as WSARecvDisconnect, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSARecvFrom function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSARecvFrom | Note When issuing a blocking Winsock call such as WSARecvFrom with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSARecvMsg function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSARecvMsg | Note When issuing a blocking Winsock call such as WSARecvMsg with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSASend function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSASend | Note When issuing a blocking Winsock call such as WSASend with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSASendDisconnect function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSASendDisconnect | Note When issuing a blocking Winsock call such as WSASendDisconnect, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSASendMsg function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSASendMsg | Note When issuing a blocking Winsock call such as WSASendMsg with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSASendTo function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > WSASendTo | Note When issuing a blocking Winsock call such as WSASendTo with the lpOverlapped parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| accept function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > accept | Note When issuing a blocking Winsock call such as accept, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| bind function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > bind | Note When issuing a blocking Winsock call such as bind, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| closesocket function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > closesocket | Note When issuing a blocking Winsock call such as closesocket, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| connect function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > connect | Note When issuing a blocking Winsock call such as connect, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| getsockopt function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > getsockopt | The socket option for which the value is to be retrieved. Example: SO_ACCEPTCONN. The optname value must be a socket option defined within the specified level, or behavior is undefined. Note When issuing a blocking Winsock call such as getsockopt, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| listen function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > listen | Note When issuing a blocking Winsock call such as listen, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| recv function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > recv | Note When issuing a blocking Winsock call such as recv, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| recvfrom function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > recvfrom | Note When issuing a blocking Winsock call such as recvfrom, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| select function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > select | Note When issuing a blocking Winsock call such as select with the timeout parameter set to NULL, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| send function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > send | Note When issuing a blocking Winsock call such as send, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| sendto function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > sendto | Note When issuing a blocking Winsock call such as sendto, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| setsockopt function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > setsockopt | The socket option for which the value is to be set (for example, SO_BROADCAST). The optname parameter must be a socket option defined within the specified level, or behavior is undefined. Note When issuing a blocking Winsock call such as setsockopt, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| shutdown function | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Functions > shutdown | Note When issuing a blocking Winsock call such as shutdown, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread. Issuing another blocking Winsock call inside an APC that interrupted an ongoing blocking Winsock call on the same thread will lead to undefined behavior, and must never be attempted by Winsock clients. |
| WSAOVERLAPPED structure | Dev Center - Desktop > Docs > Windows Development Reference > Networking > Windows Sockets 2 > Winsock Reference > Winsock Structures and Typedefs > WSAOVERLAPPED | Reserved for internal use. The Internal member is used internally by the entity that implements overlapped I/O. For service providers that create sockets as installable file system (IFS) handles, this parameter is used by the underlying operating system. Other service providers (non-IFS providers) are free to use this parameter as necessary. |
| WLX_NOTIFICATION_INFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Authentication > About Authentication > Winlogon and Credential Providers > Winlogon and GINA > Winlogon Notification Packages > Winlogon Notification Package Reference > Event Handler Function Prototype > WLX_NOTIFICATION_INFO | Reserved for internal use. Reserved for internal use. |
| RegisterNotification function | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Authentication > Authentication Reference > Authentication Functions > RegisterNotification | Reserved for internal use. Reserved for internal use. |
| IX509Extension interface | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Certificate Enrollment API > Certificate Enrollment API Reference > CertEnroll Interfaces > Certificate Extension Interfaces > IX509Extension | The Certificate Enrollment API contains the following interfaces, derived from IX509Extension, that you can use to create the various extensions used most commonly in a public key infrastructure (PKI) that relies on a Windows certificate server.Note Do not use the IX509Extension base interface to represent any extension that can be represented by one of the following interfaces. Enrollment behavior is undefined if the appropriate interface is not used. |
| IX509PrivateKey::LegacyCsp property | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Certificate Enrollment API > Certificate Enrollment API Reference > CertEnroll Interfaces > Certificate Signature and Key Interfaces > IX509PrivateKey > IX509PrivateKey Properties > LegacyCsp Property | Because a previously specified ProviderName is not affected by setting the LegacyCsp property, setting a LegacyCsp that is inconsistent with the ProviderName property will result in undefined behavior, likely a failure when creating or opening a private key. |
| IX509PrivateKey::ProviderType property | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Certificate Enrollment API > Certificate Enrollment API Reference > CertEnroll Interfaces > Certificate Signature and Key Interfaces > IX509PrivateKey > IX509PrivateKey Properties > ProviderType Property | Because a previously specified ProviderName is not affected by setting the ProviderType property, setting a ProviderType that is inconsistent with the ProviderName property will result in undefined behavior, likely a failure when creating or opening a private key. We recommend that you set the ProviderType property only when attempting to force the use of the default provider for the specified type as discussed above. |
| ACS-Maximum-SDU-Size attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > ACS-Maximum-SDU-Size | The ACS-Maximum-SDU-Size attribute is for internal use only. Based on RFC2210. |
| ACS-Minimum-Delay-Variation attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > ACS-Minimum-Delay-Variation | The ACS-Minimum-Delay-Variation attribute is for internal use only. Based on RFC2210. |
| ACS-Non-Reserved-Max-SDU-Size attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > ACS-Non-Reserved-Max-SDU-Size | The ACS-Non-Reserved-Max-SDU-Size attribute is for internal use only. Based on RFC2814. |
| DS-Core-Propagation-Data attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > DS-Core-Propagation-Data | The DS-Core-Propagation-Data attribute is for internal use only. |
| DS-Heuristics attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > DS-Heuristics | Reserved for internal use. Reserved for internal use. Reserved for internal use. Reserved for internal use. |
| Ipsec-ID attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > Ipsec-ID | The Ipsec-ID attribute is for internal use only. |
| Ipsec-ISAKMP-Reference attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > Ipsec-ISAKMP-Reference | The Ipsec-ISAKMP-Reference attribute is for internal use only. |
| Ipsec-Owners-Reference attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > Ipsec-Owners-Reference | The Ipsec-Owners-Reference attribute is for internal use only. |
| Netboot-Mirror-Data-File attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > Netboot-Mirror-Data-File | The Netboot-Mirror-Data-File attribute is reserved for internal use. |
| Prefix-Map attribute | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Attributes > All Attributes > Prefix-Map | The Prefix-Map attribute is for internal use only. |
| Ipsec-ISAKMP-Policy class | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Classes > All Classes > Ipsec-ISAKMP-Policy | The Ipsec-ISAKMP-Policy class is for internal use only. |
| Ipsec-Negotiation-Policy class | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directories > Active Directory Schema > Classes > All Classes > Ipsec-Negotiation-Policy | The Ipsec-Negotiation-Policy class is for internal use only. |
| ADS_SEARCH_COLUMN structure | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Directory Services > Directory Access Technologies > Active Directory Service Interfaces > Active Directory Service Interfaces Reference > ADSI Structures > ADS_SEARCH_COLUMN | Reserved for internal use by providers. |
| MIIS_PasswordChangeQueue Class | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Directory, Identity, and Access Services > Identity Services > Identity Lifecycle Manager 2007, Feature Pack 1 Developer Reference > WMI Provider Reference > Classes > MIIS_PasswordChangeQueue | Note Set this property only when creating a search query to return MIIS_PasswordChangeQueue objects. Do not access this property from a returned object. This property is never set on the objects that are returned from a query. |
| PPP_EAP_ACTION enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Extensible Authentication Protocol > Extensible Authentication Protocol Reference > EAP Enumerations > PPP_EAP_ACTION | Reserved for system use. Reserved for system use. |
| RAS_AUTH_ATTRIBUTE_TYPE enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Extensible Authentication Protocol > Extensible Authentication Protocol Reference > EAP Enumerations > RAS_AUTH_ATTRIBUTE_TYPE | Reserved for internal use only. Reserved for internal use only. Reserved for internal use only. Reserved for internal use only. |
| ATTRIBUTEID enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Network Policy Server > Server Data Objects > Server Data Objects Reference > Server Data Objects Enumerations > Alphabetical Listing > ATTRIBUTEID | This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. This attribute is reserved for system use. |
| IPC_PROMPT_CTX structure | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Rights Management > Active Directory Rights Management Services SDK 2.0 > AD RMS reference > Structures > IPC_PROMPT_CTX | Do not access the network. Use of this flag will cause the IPCERROR_NEEDS_ONLINE error to be returned if accessing the network is required. |
| Built-in and Account Domains | Dev Center - Desktop > Docs > Windows Development Reference > Security and Identity > Security Management > About Security Management > LSA Policy > Built-in and Account Domains | primary domain, the account domain is used to house all accounts that provide access to the computer. On a system that is part of a network, the computer's account domain is used to house accounts that do not access network resources. Accounts that require access to the network must be defined in the account domain of a domain controller. |
| FsrmAccountType enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Server Technologies > File Server Resource Manager > FSRM Reference > FSRM Enumerations > FsrmAccountType | This value is reserved for internal use. |
| CLUSTERVERSIONINFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Server Technologies > Windows Clustering > Failover Cluster APIs > Failover Cluster API Reference > Failover Cluster Structures > Utility Structures > CLUSTERVERSIONINFO | This value is reserved for internal use. |
| Shortcut Keys: UI Text Guidelines | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Microsoft Management Console (MMC) > Welcome to the MMC 3.0 Guidelines > Common UI Controls and Text Guidelines > Shortcut Keys > Shortcut Keys: UI Text Guidelines | CTRL+A Select All CTRL+C Copy CTRL+F Find CTRL+N New CTRL+O Open CTRL+P Print CTRL+S Save CTRL+V Paste CTRL+X Cut CTRL+Y Redo CTRL+Z Undo F1 Display contextual Help window. SHIFT+F1 Activate context-sensitive Help mode (What's This?). SHIFT+F10 Display shortcut menu. SPACEBAR Select (same as primary mouse button click) ESC Cancel ALT Activate or inactivate menu bar mode. ALT+TAB Display next primary window (or application). ALT+ESC Display next window. ALT+SPACEBAR Display shortcut menu for the window. ALT+HYPHEN Display shortcut menu for the active child window (MDI). ALT+ENTER Display property sheet for current selection. ALT+F4 Close active window. ALT+F6 Switch to next window within application (between modeless secondary windows and their primary window). ALT+PRINT SCREEN Capture active window image to the Clipboard. PRINT SCREEN Capture desktop image to the Clipboard. CTRL+ESC Open the Start menu on the taskbar. CTRL+F6 Display next child window (MDI). CTRL+TAB Display next tabbed page or child window (MDI). CTRL+ALT+DEL Reserved for system use. ConceptsAccess Keys |
| IScheduledWorkItem::EditWorkItem method | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Task Scheduler > Task Scheduler Reference > Task Scheduler Interfaces > Task Scheduler 1.0 Interfaces > IScheduledWorkItem > IScheduledWorkItem::EditWorkItem | Reserved for internal use; this parameter must be set to zero. |
| TASK_TRIGGER structure | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Task Scheduler > Task Scheduler Reference > Task Scheduler Structures and Unions > TASK_TRIGGER | For internal use only; this value must be zero. For internal use only; this value must be zero. |
| Accessing Performance Data in C++ | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > Using WMI > Creating WMI Clients > Monitoring Performance Data > Accessing Performance Data in C++ | the IWbemObjectAccess interface is optimized for speed, the interface is not intrinsically threadsafe. Therefore, during a refresh operation, do not access the refreshable object or enumeration. To protect objects across threads during |
| Supporting Partial-Instance Operations | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > Using WMI > Creating WMI Providers > Developing a WMI Provider > Writing an Instance Provider > Supporting Partial-Instance Operations | Do not access the context object after you return it to WMI during a reentrant call; other providers may modify the property lists or other values during reentrancy. You can examine or modify the context object only for the duration of the |
| Provider Hosting and Security | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > Using WMI > Maintaining WMI Security > Securing Your Provider > Provider Hosting and Security | For internal use only. Not supported. |
| IWbemLocator::ConnectServer method | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > COM API for WMI > IWbemLocator > IWbemLocator Methods > ConnectServer Method | Reserved for internal use. Do not use. |
| MI_Class structure | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > Management Infrastructure API For WMI > MI Structures And Unions > MI_Class | Reserved for internal use. |
| MI_Context structure | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > Management Infrastructure API For WMI > MI Structures And Unions > MI_Context | Reserved for internal use. |
| MI_Session structure | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > Management Infrastructure API For WMI > MI Structures And Unions > MI_Session | For internal use only. For internal use only. |
| Win32_DisplayControllerConfiguration class | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > WMI Classes > Win32 Classes > Win32_DisplayControllerConfiguration | Current number of color index entries reserved for system use. This value is only valid for display settings that use an indexed palette. Indexed palettes are not used for color depths greater than 8 bits per pixel. If the color depth is more than 8 bits per pixel, this value is set to NULL. Current number of color index entries reserved for system use. This value is only valid for display settings that use an indexed palette. Indexed palettes are not used for color depths greater than 8 bits per pixel. If the color depth is more than 8 bits per pixel, this value is set to NULL. |
| Win32_VideoConfiguration class | Dev Center - Desktop > Docs > Windows Development Reference > System Administration > Windows Management Instrumentation > WMI Reference > WMI Classes > Win32 Classes > Win32_VideoConfiguration | Current number of color index entries reserved for system use. This value is only valid for display settings that use an indexed palette. Indexed palettes are not used for color depths greater than 8 bits per pixel. If the color depth is more than 8 bits per pixel, this value is set to NULL. |
| Array Manipulation Functions | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Automation > Reference > Conversion and Manipulation Functions > Array Manipulation Functions | The arrays passed by IDispatch::Invoke within VARIANTARG are called safearrays. A safearray contains information about the number of dimensions and bounds within them. When an array is an argument or the return value of a function, the parray field of VARIANTARG points to an array descriptor. Do not access this array descriptor directly, unless you are creating arrays containing elements with nonvariant data types. Instead, use the functions SafeArrayAccessData and SafeArrayUnaccessData to access the data. |
| VARENUM enumeration | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Automation > Reference > Dispatch Interfaces > IDispatch > VARENUM | VT_BSTR_BLOB is reserved for system use. |
| CLSCTX enumeration | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Component Object Model (COM) > COM Fundamentals > Reference > Enumerations > CLSCTX | Note This flag is reserved for internal use and is not intended to be used directly from your code. Note This flag is reserved for internal use and is not intended to be used directly from your code. |
| CoCreateFreeThreadedMarshaler function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Component Object Model (COM) > COM Fundamentals > Reference > Functions > CoCreateFreeThreadedMarshaler | Great care should be exercised in using the CoCreateFreeThreadedMarshaler function. This is because the performance of objects which aggregate the free-threaded marshaler is obtained through a calculated violation of the rules of COM, with the ever-present risk of undefined behavior unless the object operates within certain restrictions. The most important restrictions are: |
| handle attribute | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Microsoft Interface Definition Language (MIDL) > MIDL Language Reference > handle | If successful, the typename_bind routine should return a valid primitive binding handle. If unsuccessful, the routine should return a NULL. If the routine returns NULL, the typename_unbind routine will not be called. If the binding routine returns an invalid binding handle different from NULL, the stub behavior is undefined. |
| PROPVARIANT structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > COM > Structured Storage > Structured Storage Reference > Structures > PROPVARIANT | VT_BSTR_BLOB0xfffbstrblobValFor system use only. VT_VECTOR can be combined by an OR operator with the following types: VT_I1, VT_UI1, VT_I2, VT_UI2, VT_BOOL, VT_I4, VT_UI4, VT_R4, VT_R8, VT_ERROR, VT_I8, VT_UI8, VT_CY, VT_DATE, VT_FILETIME, VT_CLSID, VT_CF, VT_BSTR, VT_LPSTR, VT_LPWSTR, and VT_VARIANT. VT_VECTOR can also be combined by an OR operation with VT_BSTR_BLOB, however it is for system use only. |
| Dynamic-Link Library Security | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Dynamic-Link Libraries > About Dynamic-Link Libraries > Dynamic-Link Library Security | Consider removing the current directory from the standard search path by calling SetDllDirectory with an empty string (""). This should be done once early in process initialization, not before and after calls to LoadLibrary. Be aware that SetDllDirectory affects the entire process and that multiple threads calling SetDllDirectory with different values can cause undefined behavior. If your application loads third-party DLLs, test carefully to identify any incompatibilities. |
| LoadLibraryEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Dynamic-Link Libraries > Dynamic-Link Library Reference > Dynamic-Link Library Functions > LoadLibraryEx | specifies a relative path, the behavior is undefined. |
| BadMemoryCallbackRoutine callback function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > BadMemoryCallbackRoutine | structures returned. Do not access that page or your application or possibly the system will crash (the specific |
| GetProcessHeaps function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > GetProcessHeaps | The GetProcessHeaps function is primarily useful for debugging, because some of the private heaps retrieved by the function may have been created by other code running in the process and may be destroyed after GetProcessHeaps returns. Destroying a heap invalidates the handle to the heap, and continued use of such handles can cause undefined behavior in the application. Heap functions should be called only on the default heap of the calling process and on private heaps that the process creates and manages. |
| HeapFree function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > HeapFree | HeapReAlloc function. If this pointer is NULL, the behavior is undefined. |
| VirtualAlloc function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > VirtualAlloc | address range which was not MEM_RESET earlier, the behavior is undefined. When you |
| VirtualAllocEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > VirtualAllocEx | address range which was not MEM_RESET earlier, the behavior is undefined. When you |
| VirtualAllocExNuma function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Memory Management Reference > Memory Management Functions > VirtualAllocExNuma | address range which was not MEM_RESET earlier, the behavior is undefined. When you |
| Getting Process Heaps | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Memory Management > Using the Memory Management Functions > Getting Process Heaps | Note that an application should call heap functions only on its default process heap or on private heaps that the application has created; calling heap functions on a private heap owned by another component may cause undefined behavior. |
| NtQueryInformationProcess function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Functions > NtQueryInformationProcess | The other members of this structure are reserved for internal use by the operating system. |
| SetThreadpoolWait function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Functions > SetThreadpoolWait | If this parameter is not NULL, it must refer to a valid waitable object. If this handle is closed while the wait is still pending, the function's behavior is undefined. |
| ZwQueryInformationProcess function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Functions > ZwQueryInformationProcess | The other members of this structure are reserved for internal use by the operating system. |
| PEB structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PEB | Reserved for internal use by the operating system. Reserved for internal use by the operating system. Reserved for internal use by the operating system. Reserved for internal use by the operating system. Reserved for internal use by the operating system. Reserved for internal use by the operating system. Reserved for internal use by the operating system. |
| PEB_LDR_DATA structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PEB_LDR_DATA | Reserved for internal use by the operating system. Reserved for internal use by the operating system. |
| PROCESS_MITIGATION_ASLR_POLICY structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PROCESS_MITIGATION_ASLR_POLICY | This member is reserved for system use. This member is reserved for system use. |
| PROCESS_MITIGATION_DEP_POLICY structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PROCESS_MITIGATION_DEP_POLICY | This member is reserved for system use. This member is reserved for system use. |
| PROCESS_MITIGATION_STRICT_HANDLE_CHECK_POLICY structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PROCESS_MITIGATION_STRICT_HANDLE_CHECK_POLICY | This member is reserved for system use. This member is reserved for system use. |
| PROCESS_MITIGATION_SYSTEM_CALL_DISABLE_POLICY structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > PROCESS_MITIGATION_SYSTEM_CALL_DISABLE_POLICY | This member is reserved for system use. This member is reserved for system use. |
| TEB structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Processes and Threads > Process and Thread Reference > Process and Thread Structures > TEB | Reserved. Do not access. Reserved. Do not access. A pointer to thread local storage data. Do not directly access. Reserved. Do not access. Reserved. Do not access. Reserved for OLE. Do not directly access. Reserved. Do not access. A pointer to thread local storage expansion data. Do not directly access. |
| Kernel object namespaces | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Remote Desktop Services > About Remote Desktop Services > Remote Desktop Services programming guidelines > Multiple-user guidelines > Kernel object namespaces | The "Session\" prefix is reserved for system use and you should not use it in names of kernel objects. In answer to your query, the "Session" prefix is reserved for system use and you should not use it in names of kernel objects. You can use "Global" and "Local". We will clarify this in the documentation. Thanks for the suggestion. |
| ChangeTimerQueueTimer function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > ChangeTimerQueueTimer | This function cannot be called while the thread is using impersonation. The resulting behavior is undefined. |
| DeleteTimerQueueTimer function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > DeleteTimerQueueTimer | This function cannot be called while the thread is using impersonation. The resulting behavior is undefined. |
| InitializeCriticalSection function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > InitializeCriticalSection | A critical section object must be deleted before it can be reinitialized. Initializing a critical section that has already been initialized results in undefined behavior. |
| InitializeCriticalSectionAndSpinCount function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > InitializeCriticalSectionAndSpinCount | A critical section object must be deleted before it can be reinitialized. Initializing a critical section that is already initialized results in undefined behavior. |
| InitializeCriticalSectionEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > InitializeCriticalSectionEx | A critical section object must be deleted before it can be reinitialized. Initializing a critical section that is already initialized results in undefined behavior. |
| InitializeSListHead function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > InitializeSListHead | A pointer to an SLIST_HEADER structure that represents the head of a singly linked list. This structure is for system use only. |
| InterlockedFlushSList function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > InterlockedFlushSList | Pointer to an SLIST_HEADER structure that represents the head of the singly linked list. This structure is for system use only. |
| MsgWaitForMultipleObjects function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > MsgWaitForMultipleObjects | If one of these handles is closed while the wait is still pending, the function's behavior is undefined. |
| MsgWaitForMultipleObjectsEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > MsgWaitForMultipleObjectsEx | If one of these handles is closed while the wait is still pending, the function's behavior is undefined. |
| QueryDepthSList function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > QueryDepthSList | A pointer to an SLIST_HEADER structure that represents the head of a singly linked list. This structure is for system use only. |
| RegisterWaitForSingleObject function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > RegisterWaitForSingleObject | If this handle is closed while the wait is still pending, the function's behavior is undefined. |
| RtlFirstEntrySList function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > RtlFirstEntrySList | A pointer to an SLIST_HEADER structure that represents the head of a singly linked list. This structure is for system use only. |
| RtlInitializeSListHead function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > RtlInitializeSListHead | A pointer to an SLIST_HEADER structure that represents the head of a singly linked list. This structure is for system use only. |
| RtlInterlockedFlushSList function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > RtlInterlockedFlushSList | A pointer to an SLIST_HEADER structure that represents the head of the singly linked list. This structure is for system use only. |
| RtlQueryDepthSList function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > RtlQueryDepthSList | A pointer to an SLIST_HEADER structure that represents the head of a singly linked list. This structure is for system use only. |
| SleepConditionVariableSRW function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > SleepConditionVariableSRW | If the lock is unlocked when this function is called, the function behavior is undefined. |
| WaitForMultipleObjects function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > WaitForMultipleObjects | If one of these handles is closed while the wait is still pending, the function's behavior is undefined. |
| WaitForMultipleObjectsEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > WaitForMultipleObjectsEx | If one of these handles is closed while the wait is still pending, the function's behavior is undefined. |
| WaitForSingleObject function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > WaitForSingleObject | If this handle is closed while the wait is still pending, the function's behavior is undefined. |
| WaitForSingleObjectEx function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Functions > WaitForSingleObjectEx | If this handle is closed while the wait is still pending, the function's behavior is undefined. |
| OVERLAPPED structure | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Synchronization > Synchronization Reference > Synchronization Structures > OVERLAPPED | The Internal member was originally reserved for system use and its behavior may change. The InternalHigh member was originally reserved for system use and its behavior may change. Reserved for system use; do not use after initialization to zero. |
| Registry Key Security and Access Rights | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Windows System Information > Registry > About the Registry > Registry Key Security and Access Rights | Reserved for system use. |
| NtQuerySystemInformation function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Windows System Information > System Information > System Information Reference > System Information Functions > NtQuerySystemInformation | The other members of the structure are reserved for internal use by the The other member of the structure is reserved for internal use by the |
| ZwQuerySystemInformation function | Dev Center - Desktop > Docs > Windows Development Reference > System Services > Windows System Information > System Information > System Information Reference > System Information Functions > ZwQuerySystemInformation | The other members of the structure are reserved for internal use by the The other member of the structure is reserved for internal use by the |
| IVMDHCPVirtualNetworkServer::ConfigureDHCPServer method | Dev Center - Desktop > Docs > Windows Development Reference > Virtualization > Microsoft Virtual Server > Microsoft Virtual Server Reference > Virtual Server Interfaces > IVMDHCPVirtualNetworkServer > IVMDHCPVirtualNetworkServer Methods > ConfigureDHCPServer Method | and networkMask for internal use. |
| Server Functions | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Accessibility > Windows Automation API > Microsoft Active Accessibility > C/C++ Reference > Active Accessibility User Interface Services > Server Functions | This function is designed for internal use by Microsoft Active Accessibility and is documented for informational purposes only. Neither clients nor servers should call this function. |
| Spreadsheet Control Pattern | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Accessibility > Windows Automation API > UI Automation > UI Automation Provider Programmer's Guide > Implementing UI Automation Control Patterns > Spreadsheet Control Pattern | The ISpreadsheetProvider::GetItemByName method is intended to provide the same kind of navigation that an application might supply with a “Jump to Label” feature. Many spreadsheet programs let specific cells be given a friendly name or label. GetItemByName enables the client to look up a cell based on its friendly name. This method should not retrieve any cells that contain the name text because the results can be highly ambiguous. If the spreadsheet program allows multiple cells in the same a spreadsheet to have the same friendly name or label, the Microsoft UI Automation behavior is undefined. |
| DEVNAMES structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Dialog Boxes > Common Dialog Box Library > Common Dialog Box Reference > Common Dialog Box Structures > DEVNAMES | Indicates whether the strings contained in the DEVNAMES structure identify the default printer. This string is used to verify that the default printer has not changed since the last print operation. If any of the strings do not match, a warning message is displayed informing the user that the document may need to be reformatted. On output, the wDefault member is changed only if the Print Setup dialog box was displayed and the user chose the OK button. The DN_DEFAULTPRN flag is used if the default printer was selected. If a specific printer is selected, the flag is not used. All other flags in this member are reserved for internal use by the dialog box procedure for the Print property sheet or Print dialog box. |
| Usability in Software Design | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Getting Started Developing User Interfaces for Windows Applications > Designing a User Interface > Usability in Software Design | For software produced for internal use, the next best reason to make usability an important part of the development process is to reduce training costs. A highly usable product is much easier for users to learn than one for which usability was not a high priority. Users learn features more quickly and retain their knowledge longer, which directly correlates to decreased training costs and time. With a better design comes better acceptance from users. The benefit with retail software is obvious: increased sales. Acceptance is also important with software developed for internal use: increased focus on user-centered design leads to increased productivity and a diminished need for support. Visibly involving users from the beginning of development also demonstrates an interest in their concerns and needs, which increases their willingness to help in the development effort. |
| MAPPING_PROPERTY_BAG structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Internationalization for Windows Applications > Globalization Services > Extended Linguistic Services > Extended Linguistic Services Reference > Extended Linguistic Services Structures > MAPPING_PROPERTY_BAG | Reserved for internal use. |
| MAPPING_SERVICE_INFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Internationalization for Windows Applications > Globalization Services > Extended Linguistic Services > Extended Linguistic Services Reference > Extended Linguistic Services Structures > MAPPING_SERVICE_INFO | Reserved for internal use. |
| Surrogates and Supplementary Characters | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Internationalization for Windows Applications > Unicode and Character Sets > About Unicode and Character Sets > Character Sets > Surrogates and Supplementary Characters | Note Standalone surrogate code points have either a high surrogate without an adjacent low surrogate, or vice versa. These code points are invalid and are not supported. Their behavior is undefined. |
| RESOURCEHEADER structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Introduction to Resources > Resource Reference > Resource Structures > RESOURCEHEADER | Values less than 256 are reserved for system use. |
| lstrcpy function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > String Functions > lstrcpy | undefined behavior if source and destination buffers overlap. |
| lstrcpyn function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > String Functions > lstrcpyn | The lstrcpyn function has an undefined behavior if source |
| StringCbCat function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCat | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCatEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCatEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCatN function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCatN | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCatNEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCatNEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCopy function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCopy | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCopyEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCopyEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCopyN function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCopyN | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbCopyNEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbCopyNEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCbPrintf function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbPrintf | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCbPrintfEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbPrintfEx | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCbPrintf_l function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbPrintf_l | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCbVPrintf function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbVPrintf | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCbVPrintfEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCbVPrintfEx | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchCat function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCat | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCatEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCatEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCatN function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCatN | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCopy function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCopy | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCopyEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCopyEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCopyN function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCopyN | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchCopyNEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchCopyNEx | Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap. |
| StringCchPrintf function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchPrintf | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchPrintfEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchPrintfEx | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchPrintf_l function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchPrintf_l | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchVPrintf function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchVPrintf | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchVPrintfEx function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchVPrintfEx | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| StringCchVPrintf_l function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Menus and Other Resources > Strings > String Reference > Strsafe Functions > StringCchVPrintf_l | Behavior is undefined if the strings pointed to by pszDest, pszFormat, or any argument strings overlap. |
| InkRecognitionModes enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > Legacy User Interaction Features > Tablet PC > Tablet PC API Reference > Core Tablet PC Reference > Core Tablet PC Enumerations > InkRecognitionModes Enumeration | For internal use only. |
| ITfReverseConversionList interface | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > Legacy User Interaction Features > Text Services Framework > TSF Reference > TSF Interfaces > ITfReverseConversionList | Represents a list of the keystroke sequences required to create a specified string. Note ITfReverseConversionList is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions. For internal use only. Note GetLength is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions. For internal use only. Note GetString is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions. For internal use only. |
| ITfReverseConversionMgr::GetReverseConversion method | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > Legacy User Interaction Features > Text Services Framework > TSF Reference > TSF Interfaces > ITfReverseConversionMgr > GetReverseConversion Method | Retrieves an ITfReverseConversion object that can perform reverse conversions. Note GetReverseConversion is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions. For internal use only. |
| Windows Touch Gestures Overview | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > Legacy User Interaction Features > Touch Input > Programming Guide > Windows Touch Gestures > Windows Touch Gestures Overview | These messages are used by the default gesture handler. Application behavior is undefined when |
| GESTUREINFO structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > Legacy User Interaction Features > Touch Input > Windows Touch Programming Reference > Windows Touch Gestures > Structures > GESTUREINFO | These messages are used by the default gesture handler. Application behavior is undefined when |
| WM_POINTERCAPTURECHANGED message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > User Input Messages and Notifications > User Input Message Reference > Messages > WM_POINTERCAPTURECHANGED | If an application selectively consumes some pointer input and passes the rest to DefWindowProc, the resulting behavior is undefined. |
| WM_POINTERDOWN message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > User Input Messages and Notifications > User Input Message Reference > Messages > WM_POINTERDOWN | If an application selectively consumes some pointer input and passes the rest to DefWindowProc, the resulting behavior is undefined. |
| WM_POINTERUP message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > User Input Messages and Notifications > User Input Message Reference > Messages > WM_POINTERUP | If an application selectively consumes some pointer input and passes the rest to DefWindowProc, the resulting behavior is undefined. |
| WM_POINTERUPDATE message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > User Interaction > User Input Messages and Notifications > User Input Message Reference > Messages > WM_POINTERUPDATE | If an application selectively consumes some pointer input and passes the rest to DefWindowProc, the resulting behavior is undefined. |
| ComboBox_GetCueBannerText macro | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > ComboBox > ComboBox Control Reference > ComboBox Control Macros > ComboBox_GetCueBannerText | If there is no cue banner text to get, the return value is FALSE. If the calling application fails to allocate a buffer, or set cchText before sending this message, undefined behavior may result and the return value may not be reliable. |
| CB_GETCUEBANNER message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > ComboBox > ComboBox Control Reference > ComboBox Control Messages > CB_GETCUEBANNER | If there is no cue banner text to get, the return value is 0. If the calling application fails to allocate a buffer, or set lParam before sending this message, undefined behavior may result and the return value may not be reliable. |
| Edit Control | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Edit Control | Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. |
| Edit_TakeFocus macro | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Edit Control > Edit Control Reference > Edit Control Macros > Edit_TakeFocus | [Intended for internal use; not recommended for use in applications. This macro may not be supported in future versions of Windows.] |
| EM_NOSETFOCUS message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Edit Control > Edit Control Reference > Edit Control Messages > EM_NOSETFOCUS | [Intended for internal use; not recommended for use in applications. This message may not be supported in future versions of Windows.] |
| EM_TAKEFOCUS message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Edit Control > Edit Control Reference > Edit Control Messages > EM_TAKEFOCUS | [Intended for internal use; not recommended for use in applications. This message may not be supported in future versions of Windows.] |
| About List-View Controls | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > List View > List-View Control Overviews > About List-View Controls | You do not access extended list-view styles in the same manner as standard window styles. You do not use the GetWindowLong and SetWindowLong functions to make extended style changes. |
| Pager | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Pager | Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. |
| Pager_SetScrollInfo macro | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Pager > Pager Control Reference > Pager Control Macros > Pager_SetScrollInfo | [Intended for internal use; not recommended for use in applications. This macro may not be supported in future versions of Windows.] |
| Rich Edit Functions | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Rich Edit > Rich Edit Control Reference > Rich Edit Functions | Note Intended for internal use; not recommended for use in applications. This function may not be supported in future versions. |
| REExtendedRegisterClass function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Rich Edit > Rich Edit Control Reference > Rich Edit Functions > REExtendedRegisterClass | [Intended for internal use; not recommended for use in applications. This function may not be supported in future versions.] |
| ITextRange2::HexToUnicode method | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Rich Edit > Text Object Model > Text Object Model Reference > Text Object Model Interfaces > ITextRange2 > HexToUnicode method | Some Unicode surrogates for hex values from 0x10000 up to 0x10FFFF are for internal use: |
| ITextRange2::UnicodeToHex method | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Rich Edit > Text Object Model > Text Object Model Reference > Text Object Model Interfaces > ITextRange2 > UnicodeToHex method | Some Unicode surrogates for hex values from 0x10000 up to 0x10FFFF are for internal use: |
| Toolbar | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Toolbar | Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. |
| Toolbar Extended Styles | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Toolbar > Toolbar Control Reference > Toolbar Control Constants > Toolbar Extended Styles | Version 5.82. Intended for internal use; not recommended for use in applications. This style gives the toolbar a vertical orientation and organizes the toolbar buttons into columns. The buttons flow down vertically until a button has exceeded the bounding height of the toolbar (see TB_SETBOUNDINGSIZE), and then a new column is created. The toolbar flows the buttons in this manner until all buttons are positioned. To use this style, the TBSTYLE_EX_VERTICAL style must also be set. Version 5.82. Intended for internal use; not recommended for use in applications. This style gives the toolbar a vertical orientation. Toolbar buttons flow from top to bottom instead of horizontally. |
| TB_SETBOUNDINGSIZE message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Toolbar > Toolbar Control Reference > Toolbar Control Messages > TB_SETBOUNDINGSIZE | [Intended for internal use; not recommended for use in applications. This message may not be supported in future versions of Windows.] |
| Tree View | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View | Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. Intended for internal use; not recommended for use in applications. |
| Tree-View Control Extended Styles | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Constants > Tree-View Control Extended Styles | Windows Vista. Intended for internal use; not recommended for use in applications. Do not collapse the previously selected tree-view item unless it has the same parent as the new selection. This style must be used with the TVS_SINGLEEXPAND style. |
| TreeView_SetHot macro | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Macros > TreeView_SetHot | [Intended for internal use; not recommended for use in applications. This macro may not be supported in future versions of Windows.] |
| TVM_SETBORDER message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Messages > TVM_SETBORDER | Intended for internal use; not recommended for use in applications. |
| TVM_SETHOT message | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Messages > TVM_SETHOT | [Intended for internal use; not recommended for use in applications. This message may not be supported in future versions of Windows.] |
| TVITEM structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Structures > TVITEM | Version 6.0 Intended for internal use; not recommended for use in applications. The tree-view control automatically determines whether the item has child items. |
| TVITEMEX structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Application UI Development > Windows Controls > Control Library > Tree View > Tree-View Control Reference > Tree View Structures > TVITEMEX | Version 6.0 Intended for internal use; not recommended for use in applications. The tree-view control automatically determines whether the item has child items. Height of the item, in multiples of the standard item height (see TVM_SETITEMHEIGHT). For example, setting this member to 2 will give the item twice the standard height. The tree-view control does not draw in the extra area, which appears below the item content, but this space can be used by the application for drawing when using custom draw. Applications that are not using custom draw should set this value to 1, as otherwise the behavior is undefined. |
| Console Input Buffer | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > Consoles > About Consoles > Consoles > Console Input Buffer | Focus and menu events are placed in a console's input buffer for internal use by the system and should be ignored by applications. |
| SHCreatePropSheetExtArray function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Functions > SHCreatePropSheetExtArray | Returns a handle to an array of property sheet handlers. Pass this value to SHAddFromPropSheetExtArray. You do not access this value directly. |
| SHGetFileInfo function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Functions > SHGetFileInfo | Retrieve the index of a system image list icon. If successful, the index is copied to the iIcon member of psfi. The return value is a handle to the system image list. Only those images whose indices are successfully copied to iIcon are valid. Attempting to access other images in the system image list will result in undefined behavior. |
| IShellItemImageFactory::GetImage method | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Interfaces > IShellItemImageFactory > GetImage | Return the item only if it is already in memory. Do not access the disk even if the item is cached. Note that this only returns an already-cached icon and can fall back to a per-class icon if an item has a per-instance icon that has not been cached. Retrieving a thumbnail, even if it is cached, always requires the disk to be accessed, so GetImage should not be called from the UI thread without passing SIIGBF_MEMORYONLY. |
| SHAnsiToAnsi function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Lightweight Utility Functions > Miscellaneous > SHAnsiToAnsi | If the pszSrc and pszDst buffers overlap, the function's behavior is undefined. |
| SHAnsiToUnicode function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Lightweight Utility Functions > Miscellaneous > SHAnsiToUnicode | If the pszSrc and pwszDst buffers overlap, the function's behavior is undefined. |
| SHMessageBoxCheck function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Lightweight Utility Functions > Miscellaneous > SHMessageBoxCheck | The flags that specify the contents and behavior of the message box. This function supports only a subset of the flags supported by MessageBox. If you use any flags that are not listed below, the function's behavior is undefined. |
| SHUnicodeToUnicode function | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > The Windows Shell > Shell Reference > Shell Lightweight Utility Functions > Miscellaneous > SHUnicodeToUnicode | If the pwzSrc and pwzDst buffers overlap, the function's behavior is undefined. |
| Saved Search File Format | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > Windows Search > Windows Search Reference > Saved Search File Format | stackIconSizeFor internal use only. Do not use.n/a displayNameFor internal use only. Do not use.n/a autoListFlagsFor internal use only. Do not use.n/a folderFlagsFor internal use only. Do not use.n/a taskFlagsFor internal use only. Do not use.n/a frequentlyUsedColumnsFor internal use only. Do not use.n/a columnChooserColumnsFor internal use only. Do not use.n/a stackListFor internal use only. Do not use.n/a providersFor internal use only. Do not use.n/a subQueriesFor internal use only. Do not use.n/a The <properties> element describes the properties of the saved search itself. Saved search files support four properties: <author>, <kind>, <description>, and <tags>. These are for internal use only. |
| ITEMPROP structure | Dev Center - Desktop > Docs > Windows Development Reference > Windows Environment Development > Windows Search > Windows Search Reference > Windows Search Structures > ITEMPROP | For internal use only. For internal use only. For internal use only. For internal use only. |
| SimIccID (MBNProfile) Element | Dev Center - Desktop > Docs > Windows Development Reference > Wireless Networking > Mobile Broadband > Mobile Broadband Profile Schema Reference > Mobile Broadband Profile Schema Elements > SimIccID (MBNProfile) Element | This element is optional and is set by the Mobile Broadband service for internal use. An application should not set this field while creating or updating a profile. |
| WLAN_SECURABLE_OBJECT enumeration | Dev Center - Desktop > Docs > Windows Development Reference > Wireless Networking > Native Wifi > Native Wifi Reference > Native Wifi Enumerations > WLAN_SECURABLE_OBJECT | This value is reserved for internal use by the Wi-Fi Direct service. |
| ONEX_CONNECTION_PROFILE structure | Dev Center - Desktop > Docs > Windows Development Reference > Wireless Networking > Native Wifi > Native Wifi Reference > Native Wifi Structures > ONEX_CONNECTION_PROFILE | A set of 802.1X flags that can be present in the profile. These flags are reserved for internal use by the 802.1X authentication module. |
| INTF_ENTRY structure | Dev Center - Desktop > Docs > Windows Development Reference > Wireless Networking > Native Wifi > Wireless Zero Configuration Reference > Wireless Zero Configuration Structures > INTF_ENTRY | Reserved for internal use. |