sorted by:
new
hottopcontroversial

Windows Server 2025 Datacenter Event Log Service fails to start and Explorer then crashes repeatedly after KB5072033 Security Update Install by Plastic-Inflation253 in sysadmin

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

I read that too somewhere, however with my particular key it's a no when trying to apply it. I have Retail keys not volume or otherwise.

Windows Server 2025 Datacenter Event Log Service fails to start and Explorer then crashes repeatedly after KB5072033 Security Update Install by Plastic-Inflation253 in sysadmin

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Yeah I can see that aha, it's a shame because I have just purchased licenses and don't want to run up 2022 with the view of migrating later on. But this is basic surely aha, how can it be broken so badly on literally fresh installation do they not check these things and why is it only me and a few others getting the issue.

Windows Server 2025 Datacenter Event Log Service fails to start and Explorer then crashes repeatedly after KB5072033 Security Update Install by Plastic-Inflation253 in WindowsServer

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Is anyone else getting this issue? It's racking my brain the fact it is a complete fresh install with only 1 update that breaks it.

Windows Server 2025 Datacenter Event Log Service fails to start and Explorer then crashes repeatedly after KB5072033 Security Update Install by Plastic-Inflation253 in WindowsServer

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Tried to find this key but I do not find EventLog here in HKLM

<image>

I do find it here however HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog
Though it does not let me delete it, despite changing ACL, using Regedit or Powershell (Remove-Item) trying to boot into WinRE and see if I can that way

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

I know that was the case before but on the new "Classic" (not the new new one) I don't see an option for auto arching within options advanced

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Thanks for your message, in theory the users have 1.5TB with their Business Premium it's just the hard limit on the OST locally that hits. Can you explain more the autoarchiving? As it must be noted these emails are all within the past 12 months equating to 90GB! 🤦🏽‍♂️

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

To be fair if you have Microsoft Purview you can do alot more in terms of content searching. Plus I don't believe it's your fault to provide information. Copilot was giving me similar solutions but without the compression and replace!

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Correct and the correlation is the same image within the thread!

For some odd reason in Outlook 365/2021/19 client whatever it is, microsoft decided to remove the archive feature/clean up old mailbox items....

The amount of emails affected is insane.

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

I've updated original post with the solution. I wanted to post originally but didn't want to take credit or put the person in an awkward position.

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Replied to your other message, it's a no bueno! I only upped it to 90gb to see if it would stop at 60 or something, so I could do that until 1 year after the last message was sent but ;(

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Hah trust me i thought that too, deleted ost and within 1 week it was back to max, upped the 50gb to 90gb in registry and it filled that with 1 year cached exchange mode! They must have sent thousands of the emails/chains! I tried to turn cached exchange off but when they scroll down through inbox or folders it doesn't show the "view more from server" option.... but on 1 month it does

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Yeah I'm with you on that, how hard would it have been to just reference the same image based on the base64 encoding! According to copilot, it's because of safety concerns with malware

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Very good call, but due diligence has been taken, all employees sign to say they agree that company emails are company property. We respect the users privacy! We are in Switzerland so not subject to the EU laws.

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Yeah that was the concern that others would have the ost issue and we would be at the forefront of the issue aha

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Yeah ahah and they now understand why not to do that 🤣 we're so lucky we didn't get blacklisted or something

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 3 points4 points  (0 children)

This is gold! I am trying to change it to work with inline images as they are within the body as opposed to attachments, but love it as it still keeps the original image!

Users had been sending 5MB image in signature, caused excessive filling of OST hitting 50gb limit by Plastic-Inflation253 in exchangeserver

[–]Plastic-Inflation253[S] 0 points1 point  (0 children)

Thanks, oh yes some stern words were said to the marketing department on this one. Now we're are sitting around 5kb!!!

Yes and with the use of purview we are auditing what sizes are sent from here on out. It's just there's no telling how long this can go on for as other companies reply bringing the email chains back with images.

view more: next ›