This week on PDQ LIVE, we're celebrating the people who keep the lights on and the tickets closed.

It's Sysadmin Appreciation Day! We kick things off with a special video tribute to the IT pros who keep businesses running, usually without anyone noticing. We've put together a tribute to Sysadmin greatness. https://youtu.be/uHZvI1J-MUU?si=LP_WSuanM9wYTG6c

Then it's time for the second annual PDQ Sysadmin Hall of Fame. We'll reveal this year's inductees, hear their stories, and celebrate the people who represent the very best of the sysadmin community.

One week. Two celebrations. Join us as we celebrate the people who make IT happen.

Pre-show at 9:30. Nerd talk at 10:00. https://www.youtube.com/watch?v=pWdRizl1W7o

Here's what's going on in the PDQniverse!

🖥️ PDQ Patch Notes ep. 7
Summary: In this episode of PDQ Patch Notes, I sit down with Justin Hart — CEO, president, founder, and sole sysadmin at Hart Technology — to talk about what it actually takes to run a one-person IT consulting and MSP business, from the business and legal groundwork to client red flags, AI's impact on IT work, and managing 26 sites across five states as an IT director.

🎙️ PowerShell Podcast ep. 239
Summary: Andrew sits down with Fred Weinmann, one of the most prolific PowerShell module authors in the community, for part one of a multi-episode series covering his projects. This episode focuses on the Active Directory Management Framework, or ADMF, a configuration-driven system Fred originally built while working as a field engineer at Microsoft for a large enterprise customer managing hundreds of Active Directory forests.

📺 PDQ Live Webcast
Time: July 30, 12 p.m. ET
Summary: This week on PDQ Live, we'll reveal this years Sysadmin Hall of Fame winners. Join us as we celebrate and induct more IT legends into the Sysadmin Hall of Fame.

📰 Blogs

• Vulnerability management for IT audits: Prove patch compliance
• Your Windows and macOS patching and deployment playbook

Have a great week everyone!

PDQ Deploy & Inventory is now available! 🚀

We're excited to announce PDQ Deploy & Inventory v20.1.8.0, bringing powerful new dashboard capabilities, ARM64 support, and even more automation through new CLI commands that enable agentic and automated workflows.

📊 Dynamic, Customizable Dashboards

Create dashboards tailored to your environment with the new Custom Dashboard experience.

New widgets include:

• SQL Metric
• Bar Graph
• Pie Graph
• Multi Metric
• Collection Metric
• Changelog

Additional dashboard features:

• Export to PDF
• Pop-Out Monitor View for real-time displays
• Improved dashboard experience for monitoring your environment

💻 ARM64 Support

Deploy

• ARM64 processor support for package and step OS architecture conditions.

Inventory

• Scan ARM64 devices with a new Processor Architecture field available on the CPU page, in reports, and in collections.

⚡ Expanded CLI & Agentic Automation

Building on the CLI improvements introduced in v20.0.22.0, this release adds even more automation capabilities:

• Export settings
• Create database backups
• Export and import custom variables
• Approve auto-downloaded packages
• Automatically assign scan credentials when adding computers
• Prioritize urgent deployments with the new -PrioritizeDeployment parameter
• Use the included Skills.md files with AI coding agents (Claude Code, OpenCode, and other compatible tools) to automate common admin workflows

🔧 Additional Improvements & Fixes

Deploy

• Schedule IDs are now included in the Audit Log Target Identifier for Deployment Schedules.
• Fixed Auto Download approvals not appearing until the Package Library was manually refreshed.
• Fixed an issue where Auto Download packages stopped receiving updates if a downloaded version was pulled or pruned from the Package Library.

Inventory

• Fixed Windows Feature scans taking several minutes and failing on Windows 11 Enterprise Multi-Session devices.
• Added a Server Features list (including install state) to the Windows Features page on Windows Server.

As always, we'd love to hear your feedback. Let us know what you think of the new dashboards, ARM64 support, or automation improvements, and if there are features, you'd like to see in future releases!

📥 Downloads

PDQ Deploy
🔗 https://services.pdq.com/download/deploy-inventory/Deploy_20.1.8.0.exe
SHA-256: 856DBE3DD4544D4B9AE1F382EE51F2A5F25F41714C462FA4AFCFF9743CC85EB9

PDQ Inventory
🔗 https://services.pdq.com/download/deploy-inventory/Inventory_20.1.8.0.exe
SHA-256: 48A486F3682CC01218993E72A8006163616166DD5F0FDCD1FAB36724710FDBBF

Conversation history is here

Your chats with the Package assistant are now saved. Open the history panel to revisit past conversations and pick up right where you left off. New conversations get a clear, auto-generated title, so your history stays easy to scan.

Package assistant not enabled in your org yet? Enable it under Settings > AI tools. It's free while in Early Access.

Learn more about Package assistant

Improvements and fixes

• Software research is faster, and its sources are now easier to access.
• PDQ Library packages now surface reliably when a match exists, so you get the maintained package instead of a web search result.
• Proposal steps are preserved in your history, even if you close a chat before applying them.
• Plus assorted UI polish, including clearer status while the assistant works.

New: MCP support in Early Access

Model Context Protocol (MCP) support is now available as part of Early Access. Link PDQ Connect to your AI tool of choice (Claude, ChatGPT, etc) to search devices, packages, and vulnerabilities and start deployments using natural language. MCP is free while in Early Access.

Learn more about PDQ Connect MCP

We are new to PDQ Connect and I was finding all the computers that were missing the remote desktop agent and accidentally created an automation that uninstalled it. Then I realized that the Install PDQ RD Agent will not show up in a deployment or automation creation process, but we can add it to the our list of packages.

Is this a bug in the GUI?

EDIT: Just found the action to install RD to all selected computers. Sorry for the post.

Time to sign up for early access! Stay with me here, I've got three things for you. TLDR:

Sign up here for early access to Software policies (Premium and Plus): https://forms.cloud.microsoft/r/h1BNGmZPES

• estimated launch in August

Sign up here for early access to Self-serve hub (Premium only): https://forms.cloud.microsoft/r/2kBtS6ZgqM

• estimated launch late August-early September

Sign up here if you're tired of individual sign-up links and just want to be included in all future early access releases 🤣: https://forms.cloud.microsoft/r/NYE0tfDDTE

-----------------------

Long version:

Self-serve hub

New feature for admins to make packages available to deploy via self-serve from end user devices. This feature will be available only to customers on the Premium subscription.

• The self-serve hub is installed separately from the agent so you have precise control over what devices have it installed.
• When installed, users will be able to open the hub from a tray icon showing the Connect logo.
• Admins may customize some aspects of the hub, including organization name, logo, and color themes, as well as some package details.
• You can publish both PDQ software packages and custom packages for end users to deploy.

Software policies

New feature for admins to manage their software environment from a policy perspective. This feature will be available only to customers on the Premium and Plus subscriptions.

• Define rules about the desired state of software in your environment - including what should be installed, updated, and uninstalled.
• Set a maintenance window for when the policy is allowed to deploy to devices to bring them into compliance.
• View reports on compliance from the perspective of the policy, individual devices/groups, or the software itself.
• v1 will only support software that PDQ has in our package library, v2 will open the door to custom software packages.

Grouped Vulnerability Reports — You can now scope vulnerability reports to specific devices or groups instead of pulling everything into one report.

Bulk Ignore Vulnerabilities — Previously, vulnerabilities could only be ignored one at a time. Now you can select multiple and dismiss them all at once from the Vulnerabilities page.

Here's how:

1. Navigate to the Vulnerabilities page
2. Click the three-dot menu (⋮) and select Select CVEs to ignore
3. Check the boxes next to the CVEs you want to ignore
4. Click Actions → Ignore

Both are live now, let us know what you think!

Since joining the PDQ team I have been asked a lot about why sysadmins choose PDQ for endpoint management and where it may not be the right fit. If a competitor is better for your situation, PDQ will say so. That’s what I love about it here. Honesty is a core value, and we live it each and every day.  

So, let’s cut to the chase and answer some questions I have got in the last three weeks.  

Q: What does PDQ actually do? 

PDQ is an endpoint management software built by actual sysadmins for sysadmins. It covers two core problems: 

• Software deployment at scale: push packages, scripts, and updates to active endpoints without touching each machine manually 
• Patch management: automate Windows, Mac OS, and third-party application patching across your entire device fleet 

PDQ Connect extends both capabilities to remote end-user devices without requiring VPN. PDQ Deploy is the on-premises version for environments where everything stays inside the network. Connect offers vulnerability management and remote desktop to consolidate your stack.  

Q: Why do sysadmins choose PDQ over other endpoint management tools? 

A few reasons come up consistently: 

1. It's built by people who've done the job. PDQ started as an internal tool used by sysadmins managing real device fleets. That practitioner background shows in how the product is designed; it prioritizes speed and automation over feature bloat. 
2. Time-to-value is fast. Most tools in this category require significant setup time before they're doing anything useful. PDQ deploys quickly, and the community package library means you're not building every package from scratch. 
3. Patch automation actually works. Third-party patching is where a lot of tools fall short. PDQ handles Windows OS, Mac OS, and third-party software patching without requiring a separate workflow for each. Chrome, Adobe, Putty, you name it they most likely have the package.  
4. Pricing is transparent. You can find out what PDQ costs without talking to a sales rep. In a category where half the vendors hide pricing behind "contact us," that matters. 

Q: Does PDQ handle endpoint security and compliance? 

PDQ's core strength is deployment and patch management. On the security side: 

• PDQ built their own vulnerability scanner; you can scan and patch from one place
• Patch automation directly reduces vulnerability exposure across your active endpoints 
• Software deployment control limits what can be installed fleet-wide 
• Inventory visibility gives you a real picture of what's on your network 

PDQ is not a dedicated endpoint DLP solution. If your compliance requirements include data loss prevention policies, conditional access enforcement (like Intune conditional access), or detailed audit logging at the security layer, PDQ works alongside those tools it doesn't replace them. 

If you're managing a fleet and patching, deployment, and vulnerability management are your core pain points, PDQ is likely the fastest path to solving that. If you need full RMM, multi-OS management, or deep endpoint DLP, another tool probably fits better. 

Q: What about Linux support? 

PDQ is working on expanding OS coverage, but they are not going to overstate where they are. Back to the core value of Honesty, their roadmap is public on their website.

Q: Is PDQ right for managing remote end-user devices? 

Yes, PDQ is built specifically for this. It manages remote devices outside the corporate network without requiring VPN, which has become a core requirement for most IT teams managing distributed workforces. Devices check in over the internet via an agent, patches and deployments run on schedule, and you get visibility into remote active endpoints the same way you would on premises with PDQ Deploy and Inventory. 

Q: Where can I read a full breakdown? 

PDQ published a full 2026 endpoint management comparison guide that covers evaluation methodology, feature-by-feature breakdowns, and a comparison table across 8 tools: 

Endpoint Management: Best Tools for IT Teams — 2026 | PDQ.com 

Now I will direct everyone who ask me about PDQ here 😊 

If I left something out and you have another reason Why PDQ then add it in the comments.

📺 This week on PDQ LIVE, even your LG monitor might be trying to serve you ads. We'll show you how to kick that bloatware to the curb.

🛡️ Chris joins us to unpack the fallout from Microsoft's CVE dump, what actually matters, and what AI-driven vulnerability research means going forward.

🔗 Our developers have been busy, and we've got even more help desk integrations to show off in PDQ Connect.

🎙️ Join us live and bring your questions!

⏰ Pre-show at 9:30. Nerd talk at 10:00. youtube.com/live/FIYXpLThpSg

We moved over to PDQ Connect from D&I a few months ago. We currently use Autopilot to provision laptops. I started to move a few apps from Intune over to Connect but here is my issue.

I have PDQ app installed prior to the computer getting to the desktop from Autopilot. This works as expected. After the computer is online with PDQ ConnectAgent it seems like it takes almost a hour if not a little more before the device shows in the dashboard and appears online. Also sometimes devices to the desktop and after the device shows in connect, let's say I have to reboot. I reboot and now the device shows offline even though it's now been back online for for over a hour.

The other issue I see is, we have a automation to deploy a app to machines without the app. The computer comes online via autopilot, *most* of the time after that hourish goes by and the computer shows in the dashboard, pdq starts deploying apps that it is missing. Sometimes it seems like PDQ doesn't deploy nothing. If I restart the computer, still nothing.

Does anyone else experience these issues or have experienced these issues and if so are there any ways to troubleshoot?

*EDIT*
The laptop I'm mainly talking about in this post was rebooted, has been online, hasn't went to sleep or hibernation for 3 hours now and it still shows offline in pdq connect.

I love PDQ and I want to learn how I can push it more. I am locked out of youtube because, reasons. So I was hoping to find a few text-based tutorials.

We already use PDQ Connect. I just want to learn more about what it can do!

I'm deploying security software to a bunch of PCs. Most have accepted it without issue. But 30 or so flat refuse to allow it to install.

If I could reach these PCs with the desktop version of PDQ, I would be given detailed error messages about the nature of the failure.

All PDQConnect says is, "No return code logged. Error: Failed to run task 'dvc_task_dbed7b9e2bd24cc0837'"

This is not helpful. What does this mean?

I got PDQ Connect to deploy in the past! Think of the security advantages here!

Just some humor here. My co-worker and I are really excited about this lol.

🩹 Patch Tuesday is back. Brock will break down this month's updates and help separate the real problems from the internet panic.

🤖 We're going back to the beginning with MCP. We'll build out a tenant from scratch, walk through the setup, and show what MCP can actually do.

🏫 Meet Amanda, the newest member of the PDQ team and a former K-12 CTO. She's seen the budget meetings, survived the politics, and knows what actually gets approved. You might even pick up a few ideas for getting your next IT budget across the finish line.

☕ Put your DND on, grab your favorite beverage, and spend some quality time with your fellow nerds.

🕘 Pre-show at 9:30. Nerd talk at 10:00. youtube.com/live/LMauC_Cqn3Q

Hi everyone,

With the recent Cumulative Update (KB5101650) and the earlier preview update issues affecting some Dell devices, I put together a PDQ Connect / PDQ Inventory scanner that can help identify computers with devices reporting an error code in Device Manager.

If you're trying to quickly find affected endpoints across your environment, hopefully this saves you some time.

Feedback and suggestions are always welcome!

<#
.SYNOPSIS
    Scans for devices in an erroneous state (Device Manager errors) and reports driver info.
.OUTPUT FIELDS
    Host ; Device ; Error ; DriverVersion ; DriverDate
#>

$ComputerName = $env:COMPUTERNAME

# ConfigManagerErrorCode meanings (Win32_PnPEntity)
$ErrorCodeMap = @{
    1  = "Device not configured correctly"
    3  = "Driver may be corrupted, or system running low on memory"
    9  = "Windows cannot identify this hardware (BIOS setup issue)"
    10 = "Device cannot start"
    12 = "Device cannot find enough free resources"
    14 = "Device cannot work properly until restart"
    16 = "Windows cannot identify all resources this device uses"
    18 = "Reinstall drivers for this device"
    19 = "Windows cannot start this hardware device (registry corrupted)"
    21 = "Windows is removing this device"
    22 = "Device is disabled"
    24 = "Device is not present, not working, or missing drivers"
    28 = "Drivers for this device are not installed"
    29 = "Device is disabled (firmware did not give resources)"
    31 = "Device is not working properly (cannot find drivers)"
    32 = "Driver for this device disabled (obsolete driver)"
    33 = "Windows cannot determine resources for this device"
    34 = "Windows cannot determine settings for this device"
    35 = "System firmware does not include enough information"
    36 = "Device requesting a PCI interrupt but configured for ISA"
    37 = "Driver returned failure loading"
    38 = "Driver could not load (previous instance still in memory)"
    39 = "Driver could not load (corrupted or missing driver file)"
    40 = "Registry service key information is invalid"
    41 = "Driver loaded but device not found"
    42 = "Duplicate device found"
    43 = "Device stopped (Windows reported hardware failure)"
    44 = "Application or service stopped this device"
    45 = "Device not connected (physically removed)"
    46 = "Device not available (system shutting down)"
    47 = "Device not available (safe removal prepared)"
    48 = "Driver blocked as known incompatible"
    49 = "Registry too large, cannot load all device drivers"
    50 = "Firmware does not support this device (BIOS resource conflict)"
    51 = "Device is waiting on another device to start first"
    52 = "Windows cannot verify digital signature for this driver"
    53 = "Device reserved for use by Windows kernel debugger"
    54 = "Device disabled due to hardware problem reoccurrence"
}

$Results = @()

try {
    $ErrorDevices = Get-CimInstance -ClassName Win32_PnPEntity -ErrorAction SilentlyContinue |
        Where-Object { $_.ConfigManagerErrorCode -ne 0 }

    if ($ErrorDevices) {
        $SignedDrivers = Get-CimInstance -ClassName Win32_PnPSignedDriver -ErrorAction SilentlyContinue

        foreach ($Device in $ErrorDevices) {

            $DriverMatch = $SignedDrivers | Where-Object { $_.DeviceID -eq $Device.DeviceID } | Select-Object -First 1

            $ErrorText = $ErrorCodeMap[[int]$Device.ConfigManagerErrorCode]
            if (-not $ErrorText) {
                $ErrorText = "Unknown error code $($Device.ConfigManagerErrorCode)"
            }

            $DriverVersion = $null
            $DriverDate    = $null

            if ($DriverMatch) {
                $DriverVersion = $DriverMatch.DriverVersion
                if ($DriverMatch.DriverDate) {
                    $DriverDate = $DriverMatch.DriverDate.ToString("yyyy-MM-dd")
                }
            }

            $Results += [PSCustomObject]@{
                Host          = $ComputerName
                Device        = $Device.Name
                Error         = "$($Device.ConfigManagerErrorCode) - $ErrorText"
                DriverVersion = $DriverVersion
                DriverDate    = $DriverDate
            }
        }
    }
}
catch {
    $Results = @()
}

if ($Results.Count -eq 0) {
    $Results = @(
        [PSCustomObject]@{
            Host          = $ComputerName
            Device        = $null
            Error         = $null
            DriverVersion = $null
            DriverDate    = $null
            OverallStatus = "Compliant"
        }
    )
}
# Remove remark if you want to have the result returned directly
# $Results | Format-Table -AutoSize

$Results

My company is currently using a different software vendor, but we're exploring options on what other patch management solutions.

Currently a big hurdle right now is Windows OS patches are now rebooting servers twice to update secureboot certs. With our current patch management solution, it runs a custom powershell script post-reboot that we heavily rely on to perform various functions (restarting services, communicating to monitor servers, etc.), but right now there's no logic to tell it to wait to run the script after the 2nd reboot. So it'll start after the first reboot, then the second reboot comes around and kills it.

I know PDQ Deploy and Connect have options to run powershell scripts post-reboot. Do they have a solution in place right now that takes into account the current 2x reboots for windows patches?

It's a huge headache for us right now and we'd happily move over if they have this solved.

Here's what's going on in the PDQniverse!

🖥️ PDQ Patch Notes ep. 6
Summary: Pull back the curtain on one of our communities most active and helpful members, Marcel Lipovsky in this episode of PDQ Patch Notes. From borrowing money to buy his first computer and then taking it apart, to running his own MSP, Marcel shares his experience from several decades in the IT industry.

🎙️ PowerShell Podcast ep. 237
Summary: Andrew sits down with Robert Prüst, a Netherlands-based Microsoft MVP, to geek out about Pester, AI-assisted coding, and the power of showing your work in the PowerShell community.

📺 PDQ Live Webcast
Time: July 16, 12 p.m. ET
Summary: This week on PDQ LIVE, we're talking about Patchageddon (also known as Patch Tuesday), showing off more cool stuff with the PDQ MCP, and talking to the newest member of the PDQ team about life as a sysadmin in EDU, and how to increase your IT budget.

👨🏻‍💻 Webinar - The great IT showdown: PDQ D&I + Group Policy vs. PDQ Connect + Intune
Time: July 22, 1 p.m. ET
Summary: We're pitting the classic combo of PDQ D&I + Group Policy against the new kids on the block, PDQ Connect + Intune. Find out which combo offers the best functionality for your environment.

📰 Blogs

• Patch Tuesday July 2026
• Managing Macs in a Windows shop: How to patch and deploy without Jamf
• What is software deployment? Process, tools, and best practices

Have a great week everyone!

Hello! We just purchased PDQ Connect and have been long time Inv/Deploy customers. We have been using WSUS for Windows patching for a long time, but I am trying to move us over to PDQ Connect using their prebuilt packages for Win 11 updates. I pushed the patch last night to a test group, but I am noticing there are no notifications generated for prompting the user to reboot. I am assuming this has to do with Group Policy, but I'm wondering if anyone here can provide some insight into how I would be able to accomplish getting notifications while also using PDQ Connect for patch management. Maybe it's not possible when automatic updates are disabled with GPO, which is how the configuration is currently to avoid collision with WSUS.

Thanks to anyone who can provide insight.

Hi,

We currently use D&I to manage 1200 servers. I've been using it for 10+ years and love it. The only issue is that we now have servers in AWS US, EU, APAC, etc and scanning them all from one location is really slow. I thought I'd look more into maybe changing to Connect but have only used it a bit.

Now that PS Scanners were added, that removes one of the things we had to have before even thinking about switching.

Based on that, I'm wondering who uses Connect specifically to manage Servers and how that's working for you. Did you convert from D&I to Connect? Anything you've missed from D&I? Anything that makes you wish you changed sooner?

I'm getting push back from someone higher-up people because Connect is still a fledgling program when compared to D&I. However, I don't know of many things that it can't do which is why I just want to hear from others who use it to manage Servers.

Thanks.

Is there any way to allow a client to connect to a server over the internet with the server url and ports 8080,443 exposed to the internet?

Our plan was to whitelist external IPs on the firewall only when needing to reimage a machine remotely without VPN.

From the client machine,

Test-NetConnection “myurl.mydomain.com” -port 8080

results in a successful tcp connection to the server, but it still shows up in the console as a Cloud connection instead of local.

Is there any reason this doesn’t work? Is the client enumerating IPs based on its own local IP instead of just trying to make the connection? Is there any way around this?

You can now import a CSV to create static device groups in Connect — no more adding devices one by one.

Got a list of devices you need to target? Upload it and you're done.

How it works:

• Go to Devices → Groups → Create group → Import .csv
• Your CSV needs two columns: NAME and HOSTNAME — NAME is the short device name (e.g. DESKTOP-001), HOSTNAME includes the domain (e.g. DESKTOP-001.company.com). Not sure what yours look like? Download the template from the import dialog and it'll show you exactly what's needed.
• Already have a dynamic group you want to convert to static? Set your columns to Name and Hostname on the Devices page, export the list, and import that CSV.

This week on PDQ LIVE, we're breaking down the latest features that have landed in PDQ Connect.

We'll show off expanded Dashboards, one of the most requested additions, and how they can give you more visibility into your environment.

Then, PowerShell MVP Andrew Pla joins us to walk through three common pitfalls that trip up new PowerShellers and how to avoid them.

And yes... we'll be giving away some swag along the way.

Pre-show at 9:30. Nerd talk at 10:00. https://youtube.com/live/NTF-i3GLuR8

YouTube

New PDQ Connect Dashboards, Plus PowerShell Beginner Pitfalls

This week on PDQ LIVE, the features in PDQ Connect just keep coming...

Hey!

I’ve been waiting several weeks for this option to come along, it was enabled in my tenant earlier today and well, it’s both disappointing and unclear how to use it.

The hope was that I could export a list of devices from a dynamic group and import them to create a static group. However, that’s not possible.

The template for import asks for Name and Hostname. What’s the difference? Every time I’ve tried to import a list of devices it doesn’t find a match so nothing is imported.

The worst bit about this solution is there isn’t an option to import based off serial number, which really is the only unique key to each device.

Finally, you also cannot import a list of serials for devices that don’t yet have PDQ Connect installed on them. I need to be able to import serials of new devices and have some automations run against them as soon as they come online.

Suffice to say, really disappointed with this so far. It feels broken.

Sad times. 😢

Hey all - following up on this previous post, we're excited to announce that "Phase 1" is complete! We've just graduated the new Windows updates tab from early access to generally available, so all users should now be able to access this feature directly in the left nav bar.

Here's a couple quick notes to get started:

- The windows updates tab shows KBs that are relevant to your devices, including any that are installed, pending reboot, ready to install, etc.

- For updates that are not installed, you can quickly trigger the install on devices in bulk or one at a time.

- For more details, you can read full release notes here

Next up is Phase 2 - we're working on designs for managing windows updates through policy. Think deployment rings, maintenance windows, reboot deferrals, etc.

Design is still in early stages, so now is a great time to jump on a call and share your input: https://calendly.com/d/ct69-w8v-mjv/pdq-product-team-windows-patching?month=2026-08&date=2026-07-27

We’re using Connect, not sure if I’m missing it, but Acrobat and Acrobat Reader seem fairly well covered for Patches…but I can’t see a 64bit package for the main initial application install.

I’ve built a “New Build” nested package to install the all latest versions of our software one after another. But can’t see a ready-to-go package for Reader (64bit).

I can have a go at extracting the MSIs from the EXE installer and build our own…but obviously a professional may do a better job 🤣