nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

21.10 breaks the stamps folder

lovell88

We currently deploy a solution that has a powershell script that copies our company made stamps to the C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps folder. This has been working fine for a long time.

With 21.10, we noticed that our script was failing. Turns out that on new installs of 21.10 (so not an update), the permissions are broken and there is no way to access this folder. As mentioned, there is no issue with upgrades or with a clean install of 21.8 and earlier.

Is this a known issue? Also, with this being broken, is there a better way for us as a company to deploy stamps for our employees to use in Bluebeam?

Thanks in advances.

Find more posts tagged with

Comments

Arthur Reed

We are seeing the exact same thing. Looks like 21.10 is doing something to the permissions of the Stamps folder at C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps. Standard users don't have access.

kcenteno

Currently having the same issue. Reports of users not having stamps anymore. We have a workaround for this but as Arthur said the permissions of the stamps folder at C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps is completely messed up.

It is telling me that even Administrators do not have access to the folder. The owner of the folder in older versions was System.

Arthur Reed

I ended up deploying a script which fixes the ProgramData Stamps location permissions and gives everyone access to it. No more complaints as of end of business today.

lovell88

Would you mind sharing your code? If so that'd be appreciated!

Arthur Reed

$Path = "C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps"


# Ensure the folder exists

if (Test-Path $Path) {


    # Grant Everyone (well-known SID S-1-1-0) Modify rights, recursive

    icacls $Path /grant "*S-1-1-0:(OI)(CI)M" /T /C


} else {

    Write-Output "Path not found: $Path"

}

Arthur Reed

If you deploy in Intune make sure you run that in the System context, not the users.

George Stamatakis

Hi everyone, thanks for raising this. In Revu 21.10, stamp storage and access behavior changed for security reasons, so Revu no longer uses the shared machine-level stamp location as the default location for user stamps.

To deploy and share a common set of stamps, we recommend storing those stamps in a customer-managed shared folder outside Revu’s default stamp location, then configuring each user’s stamp path to point to that shared location. This allows your IT team to manage access, permissions, and deployment according to your organization’s security policies.

lovell88

Thanks for the update. We will change what we are doing. But I should say — and I know I am speaking for most people responsible for distributing your software and making sure you get paid — introducing breaking changes like this and not communicating them is bad form. It shouldn't take community posts and support tickets that go unanswered for days to discover our processes were broken by your purposeful design. I would hope this improves in the future. If you make IT upset, it will just make it hard for us to continue to recommended it.

(Yes, I know it sounds entitled but stuff like this gets so frustrating sometimes)

Scott Reid

Our users who have created their own custom stamps have now all lost access to them. I assume this was an oversight and not intentional, but it's costing us time to remediate it.

Scott Reid

We deployed this detection and remediation script via intune which is working.   It's complete in that it copies the old stamp folder contents to every user profile, emulating the previous behavior.   That's probably  overkill in most circumstances.   Note the detection will fail if the user has already created new stamps in the new location.




fixstamp_detection.ps1

# Get logged-in user

$user = (Get-CimInstance Win32_ComputerSystem).UserName

if (-not $user) {

    Write-Output "No logged-in user detected"

    exit 0  # Don't trigger remediation if no user session

$username = $user.Split('\')[-1]

$userProfile = "C:\Users\$username"

# Target Bluebeam stamps path

$destination = Join-Path $userProfile "AppData\Roaming\Bluebeam Software\Revu\21\Stamps"

# Check if path exists and contains files

if (Test-Path $destination) {

    $files = Get-ChildItem -Path $destination -Recurse -File -ErrorAction SilentlyContinue

    if ($files.Count -gt 0) {

        Write-Output "Stamps already present for $username"

        exit 0  # Compliant

Write-Output "Stamps missing for $username"

exit 1  # Non-compliant → trigger remediation


Fixstamp.ps1

$source = "C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps"

if (-not (Test-Path $source)) {

    Write-Error "Source path does not exist: $source"

    exit 1

# Get interactive logged-in users (handles console + RDP)

$loggedOnUsers = Get-CimInstance Win32_ComputerSystem | Select-Object -ExpandProperty UserName

if (-not $loggedOnUsers) {

    Write-Output "No interactive user session found. Exiting."

    exit 0

foreach ($user in $loggedOnUsers) {

    try {

        $username = $user.Split('\')[-1]

        $userProfile = "C:\Users\$username"

        if (-not (Test-Path $userProfile)) {

            Write-Warning "Profile path not found for $username"

            continue

        $destination = Join-Path $userProfile "AppData\Roaming\Bluebeam Software\Revu\21\Stamps"

        # Ensure destination exists

        if (-not (Test-Path $destination)) {

            New-Item -Path $destination -ItemType Directory -Force | Out-Null

        # Copy files

        Copy-Item -Path "$source\*" -Destination $destination -Recurse -Force -ErrorAction Stop

        Write-Output "Successfully copied stamps for $username"

    } catch {

        Write-Warning "Failed for $user : $_"

Scott Reid

Apologies for that horrendous formatting

Ian Thick

this is very annoying. our Bluebeam is not centrally managed by our IT team and all stamps are now unavailable for people who get new laptops etc. even a notification would have helped me not waste so long trying to get the stamps re-loaded and I've got colleagues with the same issue.

Welcome!

It looks like you're new here. Sign in or register to get started.