You find a bug, reach for Greenshot to crop and annotate it, and the installer bounces off a policy that blocks anything not on IT's approved list. The ticket is still open. The screen still needs capturing. And you are not getting admin rights today.
Why IT blocks Greenshot in the first place
Greenshot is open source and harmless, but that is not what a locked-down laptop checks. Managed devices run allowlists: software that is not pre-approved cannot install, and an .exe or .msi that writes to the registry trips the same rule whether it came from a sketchy site or SourceForge. Some environments also block portable builds that try to run from a USB stick or a Downloads folder. The policy is not about Greenshot specifically. It is about anything that lands outside the catalog.
Getting an exception approved means a ticket, a security review, and a wait measured in days or weeks. Meanwhile the bug you need to file is a five-minute job that has turned into a dead end. The usual workaround, hitting PrtScn and pasting into an email, gives the developer a raw full-screen image with no crop, no arrow, and no note about which of the forty elements is broken.
What still works when nothing can be installed
The browser is already approved. It renders pages, it has a built-in screen-sharing API, and a web app running inside it does not install anything to your machine. That is the whole reason a browser-based capture tool clears a policy that stops Greenshot: there is no .exe, no extension to vet, nothing that touches the registry. You open a tab and work.
Cobalt Capture runs entirely in that tab. Click Capture screen, pick the window your browser is prompting about, and the current frame is grabbed as a still. From there you do the Greenshot job: crop the image down to the broken region, drop numbered pins on the exact spots, and draw an arrow or a box in a bright color. The pins and drawings are baked into the exported image, so the developer opening it sees precisely what you marked instead of guessing. If you already have a screenshot saved, paste it or drag it in instead of capturing fresh. The full picture of what a no-install Greenshot alternative covers is on its own page, but the short version is: capture, crop, mark, share, no admin password required.
From a cropped still to something the developer can act on
Annotating is half the job. The other half is getting it to the person who fixes it in a form they can act on. Greenshot saves a file you then have to attach somewhere. Cobalt skips that step. Each screenshot becomes an item, you add a comment by typing or by dictating with the browser's speech recognition, and on Publish you get a short link anyone can open.
That link matters more than a file attachment. The person receiving it does not need an account or an install either, which is the same problem you just hit, solved on their end too. They open the link and read the review, including a clean read-only page if they only need to scan it. If they work in GitHub, a signed-in owner can send the review straight into a repository as an issue. Same capture, whatever the receiver needs.
A few habits carry over cleanly from Greenshot. Crop tight so the developer is not hunting across the whole window. Use numbered pins to set the order you want them read in. Keep each text label to a single short line, because that is what fits on an annotation without turning the image into a wall of text.
The one thing that is different: cost and the 7-day rule
Cobalt Capture is free to try with no password and no credit card: unlimited reviews and screenshots, and it asks for an email only when a review is ready so it can send you the link. There is one honest catch worth knowing up front. After 7 days, a review goes read-only for you, the owner. Editing, exports, and Send to GitHub stop. The shared link keeps working for everyone you sent it to, comments included, and nothing is deleted.
If you file bugs regularly and want reviews to stay editable past that window, Pro is $5 a month or $50 a year, reopens read-only reviews instantly, and cancels any time. The full pricing is laid out plainly. For a one-off bug on a laptop where you cannot install Greenshot, the free tier does the job: capture, annotate, publish, send the link before the week is out.
If the receiver is on a phone, note that phone browsers cannot capture the screen. The flow there is to take a normal screenshot and add it. On your locked-down desktop, though, the browser capture works directly. Start a review in a browser tab and you are past the install wall in the time it would have taken to file the IT exception request.