Skip to main content

Posts

Windows 11 22H2 unable to connect to some Windows 10 via RDP

Windows 11 22H2 unable to connect to some Windows 10 via RDP I have one machine that got pushed an upgrade from Windows 10 to Windows 11 22H2. Before the upgrade remote desktop was working to all of my Windows machines.  After the upgrade to Windows 11 22H2 RDP only works for certain machines. It was working for domain joined machines and machines that were using default local/domain policies related to RDP.  Below was the error message I am getting from RDP client (Microsoft Windows 11 Version 22H2 [Version 10.0.22621.1344]) [Window Title] Remote Desktop Connection [Content] An internal error has occurred. [^] Hide details  [OK] [Expanded Information] Error code: 0x4 Extended error code: 0x0 Timestamp (UTC): 03/04/23 04:00:05 AM Press Ctrl+C to copy.   As a workaround, on the target machine (RDP server), change the following policy using gpedit.msc . Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Remote Desktop Services | Remote Deskto

Microsoft Visual C++ Runtime Library - Debug Assertion Failed!

Microsoft Visual C++ Runtime Library - Debug Assertion Failed! Running an application in a debug environment throws the following assertion message. --------------------------- Microsoft Visual C++ Runtime Library --------------------------- Debug Assertion Failed! Program: x:\test\myapp.exe File: minkernel\crts\ucrt\src\appcrt\heap\debug_heap.cpp Line: 996 Expression: __acrt_first_block == header For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. (Press Retry to debug the application) --------------------------- Abort   Retry   Ignore    --------------------------- In my specific case, this was caused by a string created in the heap by a DLL and freed in the executable.  The DLL was built using /MDd [ Configuration Properties | C/C++ | Code Generation | Runtime Library = Multi-threaded Debug DLL (/MDd) ] and the executable was built /MTd with MFC as static library [ Configuration Properties | C/C++ | Code Generation | Runti

CPP Quick Guide

Basics Hello world User input While loop If statement For loop Switch statement Read file using ifstream Write to a file using ofstream Containers Basic usage of std::list Basic usage of std::map Basic usage of std::vector Data type conversion Windows API with Exmaples DeviceIoControl FindFirstVolumeW GetDiskFreeSpaceExW GetLogicalDrives GetLogicalDriveStrings C++/WinRT C++/WinRT Hello World Qt Cross-platform Installing Qt Creator 9.0.1 on Windows 10 Qt console hello world Qt Widget hello world Qt Widget hello world code only Keywords: C++, Qt, Programming, Tutorial

C++/WinRT Hello World

C++/WinRT Hello World This is a quick start quide to prepare a development environment to develop against C++/WinRT. System: Development OS: Windows 10 Pro 22H2 Target: Windows 10 LTSB build 10.0.14393 IDE: Visual Studio 2022 (used 17.4.4) Install Visual Studio 2022 Universal Windows Platform development workload. The following is very _important_ as this is what will allow you to create C++/WinRT project. Check C++ (v143) Universal Windows Platform tools , doing so will also enable and install corresponding SDK. Set back and relax as this will download ~24GB of data from Microsoft. After installing Visual Studio, create Windows Console Application (C++/WinRT) For the Minimum version, select Windows 10 Anniversary Update (10.0; Build 14393) The template should look like below If all is well, running it should look like below Keywords: Visual Studio, C++/WinRT

Getting the last error code while debugging even if the Win32 API returned value was not saved

Getting the last error code while debugging even if the Win32 API returned value was not saved It is not uncommon that a Win32 API call return value is not checked in code. This information can prove to be very invaluable while debuging. Fortunately, Visual Studio saves pseudovariables which includes the value normally returned by GetLastError function. To view what would have returned by GetLastError use $err,hr in the Watch window. Refs: Visual Studio Pseudovariables Tags: Visual Studio, CPP

Getting 'You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode' after rebooting Linux Mint 21.1 Vera

On my Linux Mint 21.1 Vera machine, rebooting the machine would show the following early in the boot process You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode. Press Enter for maintenance (or press Control-D to continue): For my specific case this happended because I have a USB drive connected to the CPU. Removing the the USB drive and rebooting the machine allow me to continue with the boot process.