DEMOCRAT ELECTION FRAUD BOMBSHELL - TIME TO CALL IN FBI DIRECTOR PATEL
Milwaukee’s Election-Night USB Error Was Caught on Camera — What the Video Proves, and What It Doesn’t
Five of nine flash drives carried audit logs instead of absentee-vote totals, delaying Milwaukee’s results in a razor-thin governor’s primary. The mistake is real. The questions about training are real. The claims of a stolen election require evidence the video does not provide.
The screen is what made the story explode
Milwaukee’s latest election-night problem was not discovered through a leak, a whistleblower or a partisan investigation.
It was caught on camera.
On the night of Wisconsin’s August 11 primary, workers at Milwaukee’s central count were supposed to export absentee-vote results from tabulating machines onto flash drives and send those drives to the Milwaukee County courthouse for reporting.
Instead, five of the nine drives contained audit logs rather than the actual results.
The mistake delayed the reporting of roughly 28,000 absentee ballots by about an hour while officials returned to central count, downloaded the correct files and delivered them to the county.
Milwaukee Election Commission executive director Paulina Gutierrez called it “human error.”
Then CBS 58 reporter A.J. Bayatpour published footage from inside the counting room.
The images showed the election software presenting workers with separate options, including “export files” and “export audit log.” When the audit-log option was selected, the screen displayed language indicating that an audit log was being exported.
That is the detail that turned an administrative mistake into a political controversy.
If the screen says “export audit log,” critics asked, how could trained election workers mistake that for exporting vote totals?
It is a fair question.
But it is not the same thing as proof of fraud.
What the video actually establishes
The strongest version of this story begins by separating what the camera shows from what people want it to prove.
CBS 58’s footage confirms that the software interface distinguished between exporting election files and exporting an audit log. The station reported that workers selected the wrong export on five machines.
The footage therefore makes a training and procedure question unavoidable.
If a worker is told to transfer election results, a screen explicitly identifying an “audit log” should be a warning that the wrong file may be selected.
That does not mean the worker necessarily understood what every menu label meant, recognized the significance of the selection, or intended to delay the results.
And the available footage does not establish a coordinated plan by five different people to manipulate the election.
The public reporting reviewed for this article does not show evidence that anyone changed vote totals, deleted ballots, added ballots or altered the underlying tabulator count.
The error involved which file was placed on the flash drives used to transmit results for reporting.
That distinction matters.
A serious operational failure can justify scrutiny without automatically becoming evidence that the election itself was stolen.
Why the mistake was not caught before the drives left
Milwaukee officials offered an explanation for why staff did not discover the problem before the flash drives reached the courthouse.
The Milwaukee Election Commission said material downloaded from the tabulators is encrypted and can only be opened by the Milwaukee County Election Commission at the county courthouse.
In other words, city workers could see that a file had been exported, but under the security process described by the commission they could not open the contents at central count and verify that the drive contained the correct vote-total file.
That explanation answers one question but creates another.
If the files cannot be opened at the point of export, the front-end procedure has to be strong enough to prevent the wrong export from happening in the first place.
That means menu design, worker training, checklists, supervision and double-verification become especially important.
The city has already said it will review procedures, staffing and training before the November election.
State Rep. Scott Krug, a Republican member of the Assembly Campaigns and Elections Committee, says that review should not be left entirely to Milwaukee.
He has called for a legislative examination of what happened.
For Milwaukee, this was not an isolated embarrassment
The reason the August mistake drew so much attention is that Milwaukee has now experienced a significant election-administration problem in three consecutive years.
The problems were not identical.
In November 2024, an election worker failed to properly seal a tabulator door at Milwaukee central count. Officials responded by recounting about 30,000 absentee ballots associated with the affected machines.
The recount created delays but did not establish that votes had been changed.
In Wisconsin’s April 2025 Supreme Court election, Milwaukee reported ballot-supply problems at dozens of polling locations. CBS 58 later reported that 69 sites experienced ballot issues and nine locations ran out of ballots.
Then came August 2026: five flash drives carrying the wrong type of file and another late-night delay.
Krug summarized the pattern bluntly: “Election after election after election. It’s not always the same issue, but there’s always a major issue.”
That is a stronger criticism than claiming the three events prove the same conspiracy.
They do not.
The 2024 sealing mistake, the 2025 ballot shortage and the 2026 export error involve different procedures, different points in the election process and different possible remedies.
What connects them is administrative reliability.
A city responsible for one of the largest concentrations of Democratic votes in a closely divided swing state cannot afford repeated mistakes that create long reporting delays and predictable public suspicion.
Milwaukee’s late totals have a structural explanation — and a political cost
Milwaukee has become famous nationally for reporting large batches of absentee votes late at night.
That pattern has repeatedly fueled claims that something suspicious is happening after the rest of Wisconsin has reported.
But there is an important legal and logistical reason for the timing.
Wisconsin is one of a small number of states that does not allow local officials to begin processing absentee ballots before Election Day.
Milwaukee processes a large absentee-ballot volume at a central-count facility. Those votes take hours to open, verify, tabulate and transport through the reporting process.
The result is a recurring political problem: the state can appear to move one way while Milwaukee’s large absentee batch remains outstanding.
Krug himself has previously argued that this timing creates conspiracy theories about late-night “ballot dumps.”
He has supported the idea of allowing absentee processing to begin on Monday before Election Day, provided it is paired with reforms at central-count locations.
That proposal would likely help Milwaukee report earlier.
But it would not, by itself, explain or prevent a worker from choosing “export audit log” instead of the correct results-export function.
That is why the 2026 incident cannot be reduced to a single legislative fix.
The governor’s race made every minute look more suspicious
The error might have remained a local administrative story if the Democratic primary for governor had not been extraordinarily close.
State Rep. Francesca Hong entered Election Day as the polling favorite.
Two late polls showed her leading Milwaukee County Executive David Crowley by roughly 20 points.
Instead, Crowley produced one of the biggest polling surprises of the primary season.
He defeated Hong by only a few thousand votes — roughly four-tenths of a percentage point.
That combination was almost designed to produce suspicion: a huge polling miss, a razor-thin final margin and a late Milwaukee reporting error on the same night.
But chronology matters.
According to CBS 58’s review of the election-night results, Crowley was already ahead by about 2,000 votes when Milwaukee’s delayed absentee totals were finally reported after 1 a.m.
The late Milwaukee batch increased his lead.
It did not transform a Hong lead into a Crowley victory.
That fact directly undercuts the most dramatic version of the allegation that the delay was engineered after officials saw how many votes Hong needed to lose.
It does not erase the USB mistake.
It does not make the training failure acceptable.
It does mean the public evidence does not support the claim that the delayed batch suddenly reversed the winner.
A polling miss is not evidence of vote manipulation
The other ingredient feeding suspicion was the pre-election polling.
Hong had been shown with a commanding lead, only to lose by a fraction of a point.
That looks extraordinary.
It is also something polling experts have explanations for that do not require election fraud.
Primary elections are notoriously difficult to survey because turnout is smaller, the electorate is less predictable and late shifts can have an outsized effect.
Wisconsin’s Democratic contest changed rapidly in its final weeks. Crowley reentered the race after suspending his campaign, gained the backing of Gov. Tony Evers and benefited from a late establishment push focused on electability.
Axios reported that Democratic strategists saw late-deciding voters moving toward Crowley in the final stretch.
The polling miss deserves scrutiny of the pollsters.
It is not, by itself, evidence that the vote count was manipulated.
What Scott Krug is actually asking for
Krug’s response is important because it is more specific than many of the fraud claims circulating online.
He is asking lawmakers to examine Milwaukee’s central-count operation and obtain a report on what went wrong, who was responsible and what should change before November.
He has also said he remains interested in allowing Monday processing of absentee ballots.
But he wants that paired with answers about central-count staffing and procedure.
“Yes, I get it’s a button that might be the problem, but that’s also a training issue,” Krug said.
That is where the strongest accountability case lies.
Election systems are supposed to anticipate human mistakes.
If five of nine export drives can leave a major city’s central-count facility with the wrong files, officials need to explain why the workflow did not include a second check capable of catching the problem before transport.
That question does not require anyone to allege a stolen election.
It requires an answer before the next one.
The FBI claim needs a careful distinction
The FBI is already involved in a separate Wisconsin election controversy.
Federal agents have been interviewing Milwaukee election workers and officials in connection with questions surrounding the 2020 presidential election.
That inquiry predates the August 2026 USB mistake.
As of August 19, I found no public confirmation from the FBI, Justice Department or Milwaukee authorities that the bureau has opened a federal investigation specifically into the August 11 flash-drive error.
That is an important distinction because statements that the FBI is “investigating Milwaukee elections” can be technically true while misleading readers into believing the bureau has already opened a case over this particular incident.
If lawmakers or candidates ask the FBI to investigate, that is a political request.
It is not proof that the FBI has accepted the request, opened an investigation or found criminal conduct.
The SAVE America Act would not fix this mistake
The original argument around the Milwaukee error has also been linked to the federal SAVE America Act.
That connection needs another distinction.
The SAVE America Act is a national voting bill focused on issues such as photo identification for federal voting, proof of U.S. citizenship for registration, access to voter-registration records and restrictions affecting mail voting.
Whatever one thinks of those policies, they do not directly address the mistake seen on Milwaukee’s export screen.
A proof-of-citizenship requirement would not stop an election worker from exporting an audit log instead of vote totals.
A national voter-ID rule would not create a second-person verification step at Milwaukee central count.
The more directly relevant reforms are procedural: better training, clearer software workflow, independent confirmation before drives leave the facility, and possibly earlier absentee processing to reduce Election Day pressure.
The Senate did leave Washington for its August recess without passing the SAVE America Act, despite pressure from President Trump and other Republicans.
But tying that congressional fight directly to Milwaukee’s USB mistake risks confusing two different election-policy debates.
There are 76 days until November — and that is the real deadline
The next federal general election is November 3.
From August 19, that leaves 76 days — not 84 — for Milwaukee and Wisconsin officials to decide what changes are necessary.
The city says voters should remain confident that its elections are administered fairly, transparently, securely and according to law.
Confidence, however, is not created by asking voters to ignore visible mistakes.
It is created by showing exactly what failed and demonstrating that the same failure cannot happen again.
The video is valuable for that reason.
It gives the public something concrete to examine.
It shows that a wrong export option was available and selected. It supports serious questions about training and quality control. It strengthens the case for a procedural review.
What it does not show is a vote being changed.
It does not show someone manufacturing a ballot.
It does not show a secret plan to wait for statewide totals and then calculate the number needed to defeat Francesca Hong.
And the election-night sequence reported by CBS 58 cuts against that theory because Crowley was already leading before the delayed Milwaukee absentee batch arrived.
That leaves Milwaukee with a problem that is serious enough without exaggeration.
For the third year in a row, a major election-administration failure has given voters a reason to question whether the city’s procedures are as reliable as they need to be.
The answer should not be to dismiss every question as a conspiracy.
It should also not be to turn every mistake into proof of a stolen election.
The stronger standard is simpler.
Show the public what happened. Identify the failure. Fix the process. Test the fix before November.
Because in a state where elections are routinely decided by razor-thin margins, Milwaukee does not need another late-night mystery.
May you like
It needs a system that leaves as little room for one as possible.
