What you’re seeing
- Accented names like José or Müller appear as José or Müller after an import or export.
- Characters are replaced with question marks or empty boxes in the resulting file or system.
- The CSV looks correct in Notepad but garbled when opened in Excel, or the other way around.
- User accounts, contacts or products were created with misspelled names after a bulk import.
- The same script gives different results on Windows PowerShell 5.1 and PowerShell 7.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The file is saved in one encoding, such as UTF-8, and read as another, such as the Windows-1252 code page.
- Windows PowerShell 5.1 and PowerShell 7 use different default encodings when writing and reading files.
- Excel opens UTF-8 CSV files without a byte order mark using the regional code page, misreading special characters.
- The source system, such as an HR or accounting package, exports in a legacy encoding that is not declared in the file.
- The data passed through more than one conversion, so already-garbled characters were encoded a second time.
Why it matters
Garbled characters look cosmetic but cause real problems. Employee names misspelled in Active Directory or Microsoft 365 show up in email signatures, directories and payroll. Customer records with mangled names lead to failed address matches, duplicate accounts and embarrassing correspondence. Once bad data is imported into several systems, cleaning it up takes far longer than preventing it. For organizations with international staff or clients, this is a recurring issue until the process is fixed.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Is the original data damaged?
Usually not. The source system normally still has the correct names; the problem is in how the file was written or read along the way.
Can the records we already imported be corrected?
In most cases, yes. An engineer can identify the affected records and correct them from the original source in a secure remote session.