Tom F

I got this message when installing the April Patch 1.0: "RAD Studio found some failed deferred Getlt packages. You can revise the list of packages that failed in the Getlt Packages dialog box, and decide to cancel them or try to process" I don't see any "list of packages that failed in the GetIt Packages dialog box." I'd like to get this installed rather than ignoring it. Below is my current Help > About screen. It says Update 3 has been installed. Is that April Patch 1.0?!

Thanks, Michael! It's sad situation that one would have to reverse engineer the installer results to try to determine what happened.

>> But you can click "Ignore Patch", this only take away the advertise from Welcome Screen, you can always choose to install selecting the patch form the list. The point of my original post is that I have no idea if the patch was successfully installed and if it wasn't, how to install it. THAT'S the question I'm asking here. I appreciate your trying to help and understand now that you do not know the answer. Hopefully someone else will have the answer.

@DelphiUdIT Thanks for posting your answer to my question about installing the patch. You said, "No, this is the note about the April Patch. Take care that this is showed ONLY IF YOU INSTALL the patch with GETIT." Unfortunately, I'm not sure I understand your answer. Are you saying the Help screen says that the patch *is* installed??? And if that's true, then can I safely click "Ignore Patch on the screen below? In your second sentence, are you saying that the problem I'm having only occurs if I install the patch with GetIt? Of course, I've already done that, so I'm not sure what I can do now. Thanks again for your help.

If you haven't tried his demo projects yet, I've attached a screen recording I just made that shows to do a simple playback with Mitov's VideoLab. It literally couldn't be easier! Although I show a no-code example here, you can definitely add code using the extensive flexibility he provides. One especially important thing when implementing any video application is to keep your app responsive. Mitov has done a wonderful job using threads to keep apps responsive. And he provides hooks where your app can get access to the video frames in real-time if you want to examine them, etc. MitovVideoDemo.mp4

Mitov's VideoLab will do this. It comes with sample projects that show how to do this with just a few lines of code. We've used his tools for 15 years. His libraries are unbelievably powerful. And GREAT support.

You may be interested in this video:

I'd been using Alexandria until this morning. For as long as I remember, Alexandria showed the UAC pop-up "Do you want to allow this app to make changes..." when started. In the past, with Alexandria (being run elevated) I occasionally encountered problems with GetIt packages and others (like Quick Access Popup) that I attributed to somehow my not installing Alexandria properly. For example, drag-and-drop using DropMaster didn't seem to work when I ran my app from inside the IDE. I had hoped that doing a clean install with a new version of RAD Studio would eliminate the UAC elevation requirement. However, having just installed Athens, I still get the same UAC elevation pop-up when starting it. Has Rad Studio always required UAC elevation? Are there ramifications to add-ins because of that? Are their ramifications of running the IDE in the required elevated status like not appearing as a drop target when dragging from an unelevated app? Is there any safe and easy way to avoid any of this other than changing my Windows UAC level on the screen below? Here's my current UAC setting:

@Gex99 It's always nice to know that someone benefited from the work I put it in to solve a problem. It was a tricky problem that, as you saw from my posts, took a while to solve. The solution I eventually found was easy to implement. I'm glad it worked for you too. Thanks for saying something.

Sorry, I don't recall if there was a problem or if it was improved. It's been a while since I used it.

As Cristian says, use a profiler! I have been happy using NexusQA profiler for many years. There are other profilers out there, some free. But, my time is worth enough that spending a little money to get a commercial product was well worth it to me. There are profiler discussions elsewhere on the forum here. Avoid AQTime. It's a good company selling an archaic, inferior (and pretty-much unsupported in my experience) Delphi Profiler. Also, evaluate your SQL. Look at the execution plan, consider stored procedures, etc. But, don't do anything until you know where your bottlenecks are in code or SQL.

Another vote for Nexus Quality Suite | NexusDB. And, another downvote for AQTime. It's been terrible for years. I'm glad that SmartBear is finally abandoning it.

@Brandon Staggs and @Lajos Juhász I agree: none of this should have been necessary. I've been using Delphi since Delphi 1 and it's only been in the past year that this problem appeared. I don't know of anything specifically on my machine that might have caused this. I didn't have the AppCompatFlags/Layers registry entry. I'm running a "stock" Win10 machine with main stream security software. I suppose it's likely I did something to cause this problem. But, that it happened on a clean install of D12 surprised me. It's hard to imagine how the problem came to be. But, I'm glad it's behind me. 🙂

FIX FOUND! My bds.exe is no longer insisting it is run with Administrator privileges. This area of Windows is new to me, so perhaps my analysis and solution below are incorrect. Please be gentle on me if I'm wrong about all this! I know of four ways that Windows determines whether an exe requires UAC Admin elevation (Run as Admin). 1. The flag/checkbox on a desktop icon's Property screen's Security tab 2. The standard registry. 3. An Application Compatibility database (?) described by wosHub (or is this just the registry as edited by Microsoft's Application Compatibility Administrator?) 4. The .exe's manifest I found an easy way to view and edit the registry keys using Nirsoft's AppCompatibilityView (https://www.nirsoft.net/utils/app_compatibility_view.html) (Of course, RegEdit would work too, but you'd have to know all the fields and flags to do it manually like that) Nirsoft's AppCompatibilityView showed that the registry contained an entry that was forcing Windows to launch bds.exe with administrative rights. (See attached screen capture of the Nirsoft app) After I deleted that entry, the bds.exe Ran as Invoker and did not require UAC elevation. I believe that the D12 installer must have added an entry to the registry that forced UAC elevation for administrative rights. I don't know why the installer would do that. Nor do I know how else that entry could have occurred. After I deleted the registry entry using Nirsoft's app, I uninstalled (thoroughly with Revo) and re-installed D12. Now, when I launched the bds.exe, it started without the UAC popup. But... I then got: Exception Exception in module coreide290.bpl at 0000F3B3. Internal Error: AppIniFile was not initialized. If I ran as Admin, I did not get that error. Other than one unresolved RSP in the old JIRA database, I could find nothing about this error. I couldn't find a file on my machine with the name "AppIniFile." And, Procmon didn't give me any further information about what was going on either. I was able to follow the instructions at https://woshub.com/how-to-disable-uac-for-specific-applications/ to create a batch file that when run, causes the bds.exe to run with RunAsInvoker. I wasn't happy with a batch file sitting between my keyboard and launching bde.exe. (For example, what would happen if I double-clicked on a .dproj in the Windows Explorer? The .bat file wouldn't be run so bds.exe would again require UAC elevation.) As an alternate approach, I followed the instructions on the above woshub page to create a registry key that would flag bds.exe to be always RunAsInvoker. Here's the key: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\\Program Files (x86)\\Embarcadero\\Studio\\23.0\\bin\\bds.exe"="RunAsInvoker" You could do the same thing more easily with Nirsoft's app using its Action menu or right-clicking on app there. I did not take the time to try the Application Compatibility Toolkit method (as described at woshub) to modify the Windows compatibility database. Like I said, this is all new to me... and apparently it's new to most people. I don't if my thinking is correct, but bds.exe is launching properly... at least for the time being. If this write-up helped you solve a problem you've been having, DM me to let me know it was worth the time I spent writing it out here! Tom

@Brian Evans That's why I'm trying to fix this.

@JonRobertson Cool suggestion! Thanks. I'd never used mt.exe. Unfortunately, the requestedExecutionLevel is as you suggested, "asInvoker" And, I am an admin:

@JonRobertson: This a totally clean install, with no additional components added. I tried your bds -r"clean" suggestion and still had the UAC elevation pop-up. I also tried your suggestion of monitoring with ProcMon and got results that don't seem to reveal anything of interest.

@David Heffernan Good question! Thanks for your suggestion. There are no compatibility settings set on the desktop icon Properties screen. This is the default icon created by the installer. And bds.exe is the same.

Good questions. Yes, default installation and I’ve added nothing to the IDE.

I'm always logged in as an admin user. The desktop shortcut created by the installer does NOT have "Run this program as admin" checked. (Good thought , though!) Running bds.exe from the File Explorer has the same problem.

I know very little about UAC settings, but I think the only way that could happen is if you had the UAC Settings screen set to "Never Notify." Is that the case?

Thanks, guys, for the feedback. Now I just have to figure why my Win10 machine is requiring a UAC elevation for a standard install from the ISO.

I hate to ask it because I've seen it asked for years and years. And, now I'm asking it ... again. And, believe me, I've looked and look in the EMB docs online and elsewhere and can't find an answer. When would the installer require me to uninstall 12, as shown below? This happens on the ISO as well as the web installer. Is this typical behavior?

I wanted to add that despite many tries over the years, the migration assistant has never worked for me, even the new and "improved" ones provided occassionally. Perhaps if I select to Uninstall on the above screen, The assistant asks if I want to back up settings so I can re-apply them in 12.1?

I'm hoping to use Virtual Box in place of VMWare Workstation Pro for development and testing. I'm hoping its snapshot feature has similar functionality to VMWare's. (And, hey, it's free, AFAIK!) But, to be honest, I don't know much about it yet and I haven't gone much further yet than thinking about it. Here's evidence that VMWare is dying. https://communities.vmware.com/t5/VMware-Workstation-Pro/High-CPU-usage-by-vmnat-exe-after-upgrade-to-VMware-Workstation/td-p/2992063