Bernabé Murillo

@angryrabbit643410

I am very alone and feeling lonely . It feels like I am an orphan. I have no frds. I feels like I am always alone. But I am here to have some frds

Puerto Peñasco, Mexico Joined Jan 2026

Only @angryrabbit643410 can see everyone listening in. Visitors see a rotating sample.

Bernabé Murillo echoed

Bernabé Murillo

@angryrabbit643410 · Jan 12, 2026

Caroline Andersen

@crazywolf555613 · Jan 12, 2026 7:25 am

Sysprep on Server 2025

I just built a new VM template (VMWare) for Server 2025 Datacenter. Once I was done, I ran sysprep, chose OOBE from the drop down, checked generalize, and chose shutdown.
Today I went to deploy the template to a VM and discovered that there was a local admin password in place. I ran sysprep again and used the reboot option this time. Upon coming up, the local admin password is still present.
Did Microsoft change the way sysprep works in 2025?
I've reviewed the setupact.log file from c:\\windows\\system32\\sysprep\\panther and can't find anything obvious that said it failed. I do wonder what the return codes under the shsetup setup mean. Is a 2 a failure? Is a 0 a success?
Under SYSPRP ActionPlatform I am see that WINRE\_Generalize was successful. Does that mean anything? I see several other generalize actions under that section were successful too.
I'm seeing 4 error lines in the setuperr.log file.
2026-01-09 07:47:23, Error SYSPRP BCD: BiUpdateEfiEntry failed c000000d
2026-01-09 07:47:23, Error SYSPRP BCD: BiExportBcdObjects failed c000000d
2026-01-09 07:47:23, Error SYSPRP BCD: BiExportStoreAlterationsToEfi failed c000000d
2

73 likes 241 responses

Bernabé Murillo

@angryrabbit643410 · Jan 11, 2026

UPS Worldship 2025 error 53670 solution

I am posting because usually I look for issues and this one had a few steps I would rather put here first
Had this error come up before DNS error 53670.
Last time I checked it out, a restart of the users pc worked for some reason. Dont have time to find root cause, especially because the firewalls havent been touched since about 3 months ago.
do some diggin, find out it still says this error, but there is a related error 31610. The solution to that was a Microsoft ODBC driver out of date. Solution from this was update to a newer version. The one that ships out with UPS worldship is like 11 for some reason. As of writing this, the version that microsoft is up to is 18.
upon downloading and installing the ODBC driver, Restarted Worldship, and turns out there was an update for some reason that wouldnt populate before restarting world ship.
instead of manually setting the settings for driver 18, just ran the update. And error is gone, also because that update included a ODBC driver!
Anyway that is my solution. I dont have a ton to work with in terms of time. But I hope this helps someone
Sources: [https://community.spiceworks.com/t/ups-worldship-cannot-connect/1082894](https://communit

19 likes 63 responses

Bernabé Murillo echoed

Bernabé Murillo

@angryrabbit643410 · Jan 10, 2026

Kassem Farhat

@kassem · Jan 9, 2026 8:03 pm

I would sign an executive order, to forbid homophobia inside the Global Virtual Trust! A BIG problem there!

~Kassem Farhat
Member of GLOBAL VIRTUAL TRUST

430 likes 532 responses

Bernabé Murillo

@angryrabbit643410 · Jan 10, 2026

my signature breakfast recipe

If you're tired of cooking eggs the same way every time, give my recipe a try 😋
Ingredients:
• 1 spoon of olive oil
4 eggs
Oats
1/2 spoon of milk (optional)
Cook everything on low heat while constantly mixing. It takes about 3-4 minutes (maximum).
It might look a little runny at first, but that's fine. I like eating it with bread 🍞

31 likes 6 responses