Então, você instalou o Windows 11 e, de repente, o Visualizador de Eventos está exibindo o erro 1108 relacionado à Auditoria de Segurança do Microsoft Windows? Pois é, esse mesmo. Talvez os logs não estejam sendo exibidos corretamente, ou você esteja apenas tentando descobrir por que seus logs de auditoria de segurança parecem estranhos. Honestamente, esse tipo de coisa pode acontecer por vários motivos — arquivos de sistema corrompidos, atualizações ausentes, problemas com serviços ou corrupção do registro.É irritante, mas geralmente existem alguns truques que resolvem isso sem precisar de medidas drásticas.
A maioria das soluções envolve mexer com arquivos de sistema, serviços ou entradas do registro, então é bom ter um backup por precaução. Nada muito complicado, mas é recomendável seguir o passo a passo. Vamos explorar algumas opções práticas — elas podem ajudar a resolver o erro ou, pelo menos, a deixar seu sistema mais estável novamente.
Como corrigir o erro 1108 no Visualizador de Eventos (Auditoria de Segurança do Microsoft Windows)
Solução 1: Use o Verificador de Arquivos do Sistema (SFC) para reparar arquivos de sistema corrompidos.
Este comando costuma ser o primeiro a ser verificado, pois, se os arquivos do sistema estiverem corrompidos, os registros podem ser interrompidos ou gerar erros. O comando SFC verifica o sistema e tenta reparar quaisquer arquivos suspeitos.É um pouco estranho, mas, em algumas configurações, ele pode apresentar erros na primeira execução ou exigir várias execuções.
- Abra o Prompt de Comando como administrador. Você pode fazer isso clicando com o botão direito do mouse no botão Iniciar e escolhendo Terminal do Windows (Admin) ou pesquisando por cmd, clicando com o botão direito do mouse e selecionando Executar como administrador.
- Digite
sfc /scannowe pressione Enter. - Aguarde. O programa irá analisar e corrigir o que for possível. Se ocorrerem erros, não se preocupe.Às vezes, é necessário executar os seguintes comandos DISM para reparar a imagem de implantação:
DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealthExecute cada comando separadamente, pressionando Enter após cada um. Isso pode levar alguns minutos. Depois de concluído, execute novamente.sfc /scannow again. The goal is to see it report no integrity violations.
Fix 2: Install Windows Updates
Windows updates include patches for bugs and security, and sometimes, the issue is because your system isn't fully up-to-date. You wouldn’t believe how often a simple update fixes log errors like this.
- Press Windows key + R to open Run.
- Type ms-settings:windowsupdate and hit Enter.
- Click the Check for Updates button. If any updates are found, hit Download & Install. Be patient, because some updates can take a while.
- Once done, reboot the system and see if the error still pops up. Sometimes, a restart after updates makes all the difference.
Fix 3: Restart the Windows Event Log Service
This service handles all the logging, so if it’s frozen or in a bad state, errors pop up. Restarting it is quick and usually helps clear log-related errors.
- Press Windows key + R, type services.msc, and hit Enter.
- In the list, find Windows Event Log. Right-click it and select Restart.
- If it’s stopped, choose Start. On some machines, this step might need a quick reboot to fully take effect.
Fix 4: Modify the Registry to Fix Audit Logging
This one is kinda “poking the system, ” but if the registry has a wrong value, logs could break. Be sure to back up the registry first—because messing with it without care can mess things up worse.
- Press Windows key + R, type regedit, and hit Enter.
- Navigate to: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > EventLog
- On the right pane, right-click Start, choose Modify.
- Set the Value Data to 1 and click OK.
- Close the editor, restart your PC, and check if logs are behaving better.
Fix 5: Remove the Dfsr Restore Subkey (If Relevant)
On some setups, the DFS Replication service might relate to this error. If you see errors linked with DFSR in Event Log, try deleting that specific registry subkey. Of course, back up first! Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfsr\Restore. Backup that key, then delete it. Afterward, restart the DFS Replication Service in Services, or just hit reboot. Might help reset whatever’s messing with log collection.
Fix 6: Run System Restore to Go Back in Time
If you’ve recently noticed this error after a Windows update or system tweak, rolling back could do the trick. System Restore isn’t perfect, but it often fixes odd issues without a full reinstall.
- Type restore in the Start search and select Create a restore point.
- Click System Restore and follow the prompts. Pick a restore point from before the error started happening.
- Let it run, then reboot, and see if the logs are back to normal.
Fix 7: Repair Windows by Doing an In-Place Upgrade
Yes, it’s a bit of a hassle, but sometimes Windows just needs a fresh install of the system files without losing your stuff. Head over to the Microsoft Windows 11 official download page.
- Download the Media Creation Tool, run it, and select Create installation media for another PC.
- Choose your USB stick—at least 8GB—and let it write the install files.
- Once done, run setup.exe from the USB inside Windows.
- Follow the prompts, select to keep files/apps/settings (if you want), and run the upgrade.
Hopefully, one of these options clears the error 1108 in your event logs. It’s kind of a mix of fixing system files, services, and sometimes registry corruption. In my experience, the SFC and Windows update steps usually do the trick, especially if the error popped out after installing updates or during system idle. Or sometimes, just a restart of the event log service makes logs behave again.
Summary
- Run
sfc /scannowto fix system file issues - Apply the latest Windows updates
- Restart the Event Log service
- Modify relevant registry entries cautiously
- Consider running System Restore if recent changes caused this
- Perform a repair install if nothing else works
Wrap-up
This sort of error can be a pain, but it’s often fixable with some patience. Most fixes are pretty straightforward—just a matter of following the steps carefully. If nothing works, a repair install might be your last resort. Fingers crossed this helps someone cut down the troubleshooting time — worked for me or at least better than a full reinstall. Good luck, and don’t forget to back your stuff up before diving into registry fixes!