Take a Windows support screenshot that shows the problem clearly

A useful support screenshot shows the error and enough of the surrounding app to explain what happened. Start with the window where the problem appears. If the message is small, also capture a closer rectangle so the text is easy to read. Before sending either image, reopen it and check that the message, relevant rule, and selected file name are legible.

Choose the view your ticket needs

On Windows, press Windows + Shift + S to open the Snipping Tool capture overlay. Choose Window to capture a selected window, or Rectangle to draw around part of the screen. Microsoft also documents Fullscreen and Freeform modes, but a support ticket usually needs a deliberate view of the affected app or message. Take the capture, then open the captured image in Snipping Tool and use Ctrl + S or Save as to save a named copy. Microsoft’s Snipping Tool guide describes these controls.

A close crop can make an error readable while removing unrelated content. It can also remove the rule or form that explains the error. These two images of a fictional upload form show the difference:

Download the full browser-page example

Download the issue rectangle

The full browser-page view includes the page’s heading and the suggested message below the upload area. The rectangle retains the accepted formats, size limit, width rule and selected filename, so it preserves the information needed to explain this rejection. If you sent only the wider view, the message might be harder to read on a small screen. Attach both when each answers a different question.

These are browser-page captures of the fictional demo page. They do not show a Windows Window-mode capture: the browser title bar, operating-system controls, and Snipping Tool interface are outside the recorded images.

Describe the action as well as the error

A screenshot records what was visible; a short sentence records what you did. In the demo, the form accepts JPEG or PNG files, sets a maximum of 500,000 bytes, and requires a width of at least 1,200 pixels. The selected mock-logo.png is 620,000 bytes and 1,200 × 900 pixels. Its width meets the stated minimum, but its byte size exceeds the stated maximum. A size rejection is therefore consistent with the displayed rule.

A ticket about that example could say:

I selected mock-logo.png, a 620,000-byte PNG measuring 1,200 × 900 pixels. The form rejected it for exceeding the 500,000-byte limit. Can you confirm whether I should reduce the file below that limit before trying again?

That gives support the action, the result, and the reason for the question. It does not label a rejection that follows the rule as a bug.

A different case would deserve different wording. If a hypothetical 50,000-byte PNG at least 1,200 pixels wide received the same size rejection, include the displayed rule and ask support to check what condition caused it. That case was not tested in the demo; the point is to report the file’s actual properties rather than assume every rejection has the same cause.

Copy the error text into the ticket as well as attaching the image. Text lets a support agent read or search the message even when the attachment is scaled down. Use the exact visible error wording in that text. If you summarize it as “upload broken,” you remove the distinction between a size restriction, an unsupported format and a dimension requirement.

Name the attachments by what they show, for example upload-form-context.png and upload-size-message.png. In the ticket, identify which image contains the rule and which one shows the closest view of the message. Include an app or browser version if you can see it, but do not delay the report to guess one.

Capture a message that disappears

If a menu or message closes before you can draw a rectangle, the current Microsoft Windows 11 guide documents a delay option in Snipping Tool. Open the app, choose a delay such as five seconds, select the desired capture mode, then select New. Use the time to reopen the menu or reproduce the message before the capture begins. Controls and labels can differ on older versions of Windows.

For a message in another window, choose Window mode and select the window that actually contains it. Check the saved image afterward: a popup might need its own capture if it is separate from the main app window. A screenshot of the main page cannot establish what an offscreen popup said. The same applies to a scrolled page: a saved image shows the visible area, so a rule above the current scroll position needs another capture or an exact text quotation.

Check the image before sending it

Reopen the saved screenshot and read it at a practical viewing size. Confirm that it contains the exact message, the relevant part of the app, and any rule needed to interpret the result. If a crop cut off a useful label, take another capture.

Also scan the whole image for information you did not mean to share, such as an account name or private file path in a real app. When possible, reproduce the issue using benign input and capture that state. If you cover information in an existing image, save a flattened copy and reopen it to inspect the result before attaching it. The fictional demo images do not contain an account.

Microsoft’s current Windows 11 instructions say snips are automatically saved to the Screenshots folder and that Snipping Tool settings can change the saving behavior or location. Save as lets you choose a file name and location for an additional copy; Ctrl + S is also documented as a save shortcut. Check your own settings and the file you intend to attach instead of assuming where a capture went.

Source note: The Windows controls and saving behavior above come from Microsoft’s linked guide. The two images are recorded captures of owned, synthetic browser-page content at a 1,200 × 900 viewport; no actual Snipping Tool capture, Windows title bar, or operating-system chrome was tested.