Help Desk Blogger

A Meta ad refund can be refused after Meta's own chat promised it. In the account behind this piece, automated support said closing a wrong ad account would refund its $75 balance to the original payment method automatically. Three months later a new ticket calls that payment non-refundable. Your card's dispute clock did not pause for any of it. So before you open another ticket, do one check: find the date of the first card statement that shows the top-up.

Why is a Meta ad refund really a card-statement deadline?

Because the one deadline we could verify belongs to your card issuer: under the FTC's guidance for US credit cards, a written dispute must reach the issuer within 60 days of the first bill showing the error.

Here is the rule's own wording, from the FTC's consumer page on disputing charges (last modified 2 April 2024, read 13 November 2026). Your letter must reach the issuer "within 60 days after the first bill with the error was sent to you." Plain reading: the clock starts at the statement, not at Meta's last reply.

Dates ignore your queue. The Secure Boot certificate that expired on 19 October 2026 and Office 2021 support, which ended on 13 October 2026, both arrived on schedule. A card dispute works the same way.

Two more details decide whether the letter counts. The FTC says to "use the address given for billing inquiries, not the address for sending your payments," so a letter to the payments address may not count. Then the issuer must acknowledge your complaint in writing within 30 days and resolve it within 90. Those two dates give the whole fight an end.

Four numbers set your room. The last card is our own arithmetic; the rest come from the sources above.

The first clock is the only one you control, and it is a letter, not a ticket. Keep proof of the day it arrived: the rule counts arrival, not posting. The other two belong to the issuer.

Worked example: take a $75 top-up whose first card-statement line is 90 days old (three months, or near enough) and a letter that needs 3 days to reach the issuer. Both are assumptions; type your own below. Days used: 90 + 3 = 93. Window: 60. Dispute days left: 60 - 93 = -33 days. Negative means the window has likely closed. In the case behind this piece, it shut about 30 days before the new ticket called the payment non-refundable.

What should you do, based on your statement's age?

The right move depends on two things you can check in minutes: how many days ago the top-up first appeared on a statement, and whether you paid with a US credit card.

Our arithmetic: 60 days less up to 10 days in the post gives the 50-day line. Find your row and read across. The 51-60 row is the trap. It looks open, but a letter posted on day 59 arrives late.

What can still go wrong with a card dispute?

A card dispute can still fail: the issuer may treat a wrong-account top-up as a charge you authorised, and a letter that arrives after day 60 loses the FTC route. Our view on the first: a grey area. The FTC lists things you "didn't accept or weren't delivered as agreed" as disputable. Whether a wrong-account top-up fits is the issuer's call. We would cite the wording anyway.

Support loops are the second risk. A founder wrote in an undated company blog post that Meta collections said "we haven't received the payment that you have made via Credit Card", and the case was closed as completed. An AdExchanger trade column of 14 March 2024 put it bluntly: "the only party to complain to is an automated rep." Both are single accounts, not statistics.

The same column reports refunds that came back as ad credits, so ask in writing whether yours is cash or credit. And do not close an account on a chat's promise. Closing cannot be undone, the same caution as with a Wemo that stopped working after Belkin's shutdown.

• The FTC lets you withhold a disputed amount, but a prepaid top-up is already paid.
• We could not read Meta's help pages. The "closing refunds automatically" line is one advertiser's report of a chat.
• No written acknowledgement after 30 days means you chase the issuer.

This week, add two numbers: the days since the first statement showing the top-up, and the days a letter needs to reach the issuer. If the total is 60 or less, send a written billing-error notice to the billing-inquiry address before you open another Meta ticket. Subtract it from 60 for your dispute days left. Over 60, or paying by debit or a card outside the US, the FTC route has probably closed or does not apply: read your card agreement and still write to Meta. Our call is wrong if your issuer rules a wrong-account top-up an authorised charge. The one check is the issuer's written answer, and the FTC's guide to disputing credit card charges is where to start.

Your friend’s laptop got 26H2 last week. Yours still says “You’re up to date.” You press Check for updates, restart, press it again, and Windows 11 26H2 not showing stays the whole story. Seven checks, in this order, will either find the reason or tell you it’s time for the manual route.

Why is Windows 11 26H2 not showing in Windows Update?

Microsoft’s release health page said on 28 October 2026 that 26H2 is available for all eligible devices, so a PC that sees nothing has a local reason: the wrong version, a missing prerequisite update, or the early-offers toggle off.

1. Read your version. Press Windows key + R and type winver. Microsoft’s KB5121794 covers only versions 24H2 and 25H2. On anything older, skip to check 7.
2. Switch on early offers. Open Settings > Windows Update and turn on “Get the latest updates as soon as they’re available”. Microsoft’s 29 September post says the 26H2 option appears there once your device is eligible.
3. Check the prerequisite. KB5121794 requires the 22 September 2026 preview update KB5124010 (24H2 build 26100.9546) or a later one. A 24H2 build ending below 9546 means install updates first.
4. Check for updates and read the whole page. If “Windows 11, version 26H2 is available” appears, select Download & install. KB5121794 says the install needs a restart.
5. Look for a hold. Microsoft may place a safeguard hold on a device with a known compatibility issue. A Learn more link may open “Safeguard holds affecting your device”.
6. Scan release health. The 26H2 page, updated 30 October 2026, lists open issues; a mitigated one on your hardware is a reason to wait.
7. Only now go manual. Microsoft’s download page offers the Installation Assistant and an x64 ISO. Run one after checks 1 to 6, not instead of them.

What does waiting on 24H2 actually cost?

Microsoft’s KB5127648 page says Windows 11 24H2 Home and Pro “has reached end of updates”, so on those PCs waiting now costs you security patches, one day at a time.

Our earlier post on the 24H2 end-of-support deadline explains the date; these four numbers set the urgency, and the 24-month window is from Microsoft’s 29 September post.

The restart figure is the reason not to fear this switch, or more exactly this latch: KB5121794 says the 26H2 features already sit inside the monthly update, dormant until the package turns them on.

KB5127648 says devices without the newer certificates still start and keep receiving updates, so Secure Boot is no reason to wait. Run our three-step Secure Boot certificate check afterwards.

Worked example: take a Home PC on 24H2 on 1 November 2026 whose owner spends 14 more days on this problem. Assumptions: Home and Pro end dates from Microsoft’s lifecycle page (24H2 on 13 October 2026, 26H2 on 9 October 2028), counted as Pacific-time dates. Unpatched days when the owner finally moves: 19 already gone since 13 October plus 14 waiting, so 33 days. Patch days left on 26H2 after that move: 708 from today to 9 October 2028, minus the 14 waited, so 694 days. The same sum on 25H2 gives 345 days left today, and moving to 26H2 adds 363 more. Now do yours: open winver, read your version, and set the calculator to match.

Which fix fits your PC after winver?

Match your winver result to one row: the version decides the route, the build decides whether you must update first, and a hold message decides whether to wait.

Row 3 catches people: winver says 24H2, the toggle is on, and still nothing, because the minimum update never installed. On Microsoft’s Q&A forum on 30 October 2026 a volunteer moderator there pointed a poster to the 26H2 ISO, while an independent advisor first asked which version the PC ran. We would put the ISO last, because it skips the diagnosis.

Friction points: holds, hardware and known issues

Holds and hardware can still stop the offer: Microsoft’s 26H2 pages do not say whether safeguard holds apply to 24H2 and 25H2 PCs, and the manual route works only on x64 processors.

Microsoft’s hold page says holds lift once the issue is resolved. That is the grey area, and our opinion is plain: if Windows shows a hold, wait, because the issue behind it is what the manual route cannot skip.

The download page says installing on an unsupported PC “is not recommended and may result in compatibility issues”, and tells Arm-based PCs to wait for Windows Update.

Release health still lists USB audio failures on USB Audio Class 1.0 devices as mitigated, not resolved. If a USB headset runs your day, read our USB audio Code 10 triage first.

• Forcing past a hold. Wrong when the known issue touches your hardware; check release health first.
• Work or school PCs. Update rings and policies still apply, so ask your admin before using an ISO.

Decide this week whether to wait for the offer or go manual. A 24H2 Home or Pro PC should not wait: once checks 1 to 5 pass and no hold shows, run the Installation Assistant. A 25H2 PC can give the offer one more week. Either way, start by writing down your winver version and build.

"Your iPhone is up to date," Settings says. Yet the last update you remember landed in spring. If that phone is an iPhone 8, an X or older, you read it right: Apple's iPhone security updates for those models stopped after 11 May 2026, while newer phones were patched again on 26 October. Before you shop or panic, check one date: the day Apple released your version.

How do I check when my iPhone was last patched?

Read your iOS version in Settings, find that exact number on Apple's security releases page, and note the date beside it; that date, not the "up to date" message, tells you whether fixes are still coming.

1. Read the version. Open Settings, General, About and note the iOS Version line.
2. Find its date. Search that number on Apple's security releases page, which lists each release's date and models.
3. Count the days. Count from that date to today.

Step three is the sum to remember: "up to date" only means no newer build exists for your model. In January 2026 an iPhone X owner on Apple's Support Community asked whether the phone was still safe for banking. Nobody could name an end date.

Is the iPhone 8 still getting security updates?

Not since 11 May 2026: Apple's last release for the iPhone 8, 8 Plus and X was version 16.7.16, and that branch sat out every later wave of fixes that reached newer models.

Apple's list shows the branch's 2026 rhythm: 26 January, 2 February, 11 March and 11 May, then silence. The May release fixed a notification bug (CVE-2026-28950) with no reported attacks. The iPhone 6s, 7 and first SE, on version 15.8.8, stopped the same day.

Then, on 26 October, version 18.7.11 for the XS and XR fixed CVE-2026-86950, a CoreGraphics bug Apple says "may have been exploited in an extremely sophisticated attack" on versions before iOS 27. Nothing shipped for iOS 16 or 15, and Apple has not said whether they carry the bug. That unknown is the real risk for an iPhone X owner, more than any one flaw, really.

Apple never announces the end. Microsoft prints its dates, as with Office 2021's end of support and the Windows 11 24H2 cut-off; Apple leaves you to infer it from a gap, and we think owners should do that sum now.

Four figures from Apple's security releases page, read 30 October 2026, show who is covered and at what cost.

The XS card deserves a second look: missing a major iOS version is not missing fixes. The patch stream is what stopped for the iPhone 8 and X.

Which models still get iPhone security updates?

Every iPhone from the XS and XR onward got a security release on 26 October 2026, while the iPhone 8, 8 Plus, X, 6s, 7 and first-generation SE have had nothing since 11 May.

Find your model and read across; versions are as of October 2026.

The middle rows split on one date: the release date, not the version number, is what to check.

Worked example: an iPhone X shows version 16.7.16 on 30 October 2026. Assume 11 May is its latest release and the branch's longest earlier 2026 gap is its normal ceiling. 11 May to 30 October is 20 + 30 + 31 + 31 + 30 + 30 = 172 days. 11 March to 11 May is 20 + 30 + 11 = 61 days. 172 divided by 61 is 2.8. Past twice, we treat the phone as unsupported for banking and passwords.

Does the iPhone 11 get iOS 27?

Yes: Apple released iOS 27 on 14 September 2026 for the iPhone 11 and later, the same floor as iOS 26, so a leak claiming four older models would be cut turned out to be wrong.

MacTrast reported on 4 June 2026 that a leaker, Instant Digital, expected iOS 27 to drop the iPhone 11, 11 Pro, 11 Pro Max and second SE. Apple's 27.2 notes say "iPhone 11 and later", and we would call selling an iPhone 11 on that rumour a mistake. It lacks only Apple Intelligence, which those notes limit to the iPhone 15 Pro and later.

• No way back. Apple says installed updates cannot be downgraded, so stay on 26.7.x until you want iOS 27.
• Bank apps follow the bank. The App Store listing's Compatibility line shows each app's minimum iOS.
• Nothing breaks on a date. Unlike Wemo plugs after Belkin's shutdown, an old iPhone keeps working unpatched.

So did they stop in May? For the iPhone 8, X, 7 and 6s, yes, as far as Apple's own list shows; for the XS and later, no. The decision is whether that old phone still deserves your passwords. This week, read your version and count the days. Past twice the branch's longest 2026 gap, move banking and password apps to a supported phone. If Apple's list shows a newer build for your model, recount before you buy.