If you have gotten the WPIE15.exe error installing VB6 the reason is probably the install source. Visual Studio 6 comes from an era where we were installing on a physical computer, which of course, had a physical CD drive, which of course, had a drive letter assigned that almost never changed. So, when you installed any Visual Studio language from a CD, which you almost always did (even if you had an iso you burned a CD for the install), the installer remembered that drive letter when you installed.
Initially, when I tested a VB6 IDE install on an Windows 11 ‘out-of-the-box’ (RTM) install, I encountered no new issues. I just got a new laptop and tried the same install method on a 21H2 (Build 22000.376) and immediately ran into an issue. The install ended with a message it had not worked and a reference to an install setting. I had never seen this previously.
Windows 11 is here. The IDE was never officially supported on Windows 10 although I, like may others, have been using it there for half a decade. So, what about Windows 11? I have done an initial test using the rules outlined in my Running the IDE on Windows 10 post. The install went OK, the IDE runs and seems to work. Until I have done an amount of work, I cannot say more but it is encouraging.
The latest compromises via the SolarWinds and Exchange ‘Hafnium’ hacks bubble up an issue I just can’t resist commenting on.
I recently purchased a 2016 Ford and found I needed to update the Sync3 software to use “CarPlay” with my phone. It sounds easy but turned out not to be.