u/Bourne069

We have used OpenVPN Community Edit on our Terminal Server for 3 years straight with zero issues. Starting yesterday we rebooted the server after doing some Windows Updates and now we are seeing major and consistent packet loss when connected to the VPN. We have tested using different WAN addresses and routes etc... it will stay connected for like 2 minutes than drop all connections for multiple minutes at a time before reconnecting.

Does anyone know if there is a known issue with recent Windows Updates that could be affecting OpenVPN!?!?! Any ideas on where to go from here?

*UPDATE*

After HOURS of troubleshooting I was able to figure out the issue. Windows Defender updated and in this update it conflicts or blocks legacy TAP drivers of OpenVPN. I added "windows-driver wintun" to my openvpn server config to force it to use the new wintun drivers instead and now I was able to connect my clients with zero pack loss!

I work in I.T. and had to recreate new RDP icons for over 60 users that I was going to deploy via an RMM. But Microsoft decided to do updates in late 2025 to RDP and its utter trash now spamming my clients with additional prompts and wont save passwords. Even after wiping credential manager and credentials out of RDP and rechecking "allow me to save credentials" everytime I open the RDP icon it says "invalid credentials" and I have to manually reenter the password and than it works...

WTF is Microsoft doing over there!?!?!?!

Clients get this everytime they connect to the server now, even through its already configured in local resources in the RDP icon...

Its annoying, dumb and cant be stopped if using the RDP "save as" function. Only way I found to fix it was to make a shortcut and convert it to an RDP connect via shortcut creation... however you lose out on local resource options doing it this way so its not a valid option for me.

Currently looking into using another RDP clients because Microsoft is just utter trash shit now.

https://preview.redd.it/5z5ln88l3zmh1.png?width=966&format=png&auto=webp&s=84fd63264f02bd29ea1cbfa3d3b3ae73af68e870

https://preview.redd.it/vzfj5iun3zmh1.png?width=395&format=png&auto=webp&s=7095ed81367bf2a3d14ff8ef47f4e5639e8bc128

I use to play in a group back in the day but most people I know stopped playing the game due to cheaters.

So now I'm exclusively solo and you are telling me adding downed mechanics to a game that already gives massive advantages to group play is acceptable some how? This is literally insane talk.

Now we solos are done for. Groups will just camp their buddies bodies, or have one hold you down while the other revives etc.... Once this is implemented there is almost zero way to compete as a solo. Trash update.

WTF!?!?!?

https://preview.redd.it/1myybwdsykih1.png?width=1841&format=png&auto=webp&s=98e894d453671c460893b7044e9d1441e5ca2595

https://preview.redd.it/2v6xgi0xykih1.png?width=574&format=png&auto=webp&s=5a9f7d3985018c8dae554def4040a955e0e08f04

Thanks for the ammo!

https://preview.redd.it/8ggasume6fih1.png?width=1441&format=png&auto=webp&s=9a57103a37933b8701369c3c0a7fe28f55561559

Literally not even joking. Every single death I have had, was from a headshot. Not a single death by anything or anywhere else on the body...

Literally an UZI mag im trying to load with ammo in raid, it will do a half circle like it about to load the mag than stops. If you try to unload it you get this error... Its happened also to a pistol I just looted off a scav so I dont think its a duping issue but more so a sync issue.

https://preview.redd.it/dqp51xirolhh1.png?width=583&format=png&auto=webp&s=1e6789f2baae2bf740a03627226ef8bf534e9c68

So I had a Galaxy 4 watch and was trying to use to to measure my Blood Ox levels during sleep. I was having issues with it not sitting right on my wrist so data would disappear on and off over the night.

Fine looked up Fitbits and saw AIR was able to record Blood Ox. So I purchased it and turned on all the sleep features. It recorded Blood Ox for 2 nights than stopped. I'm unable to get it to record anymore.

To top it off for some legal reason (because Google didn't certify the Blood Ox part of the Fitbit) they no longer offer minute by minute measurements and now the UI only provides a single dot of AVG Blood Ox levels.

This is insanely dumb and stupid for a brand new product. This is GOOGLE how are you not able to certify your devices properly!?!!??!?!

This device is utterly useless to me now and because I threw away the original box by mistake I can no longer return it.

Dont waste your time with the Fitbit Air, literally buy anything else.

Literally can't go 3 raids without running into obvious cheater. They arnt even trying to hide it anymore.

This last one I had a phone call to take so hide into shipping containers near where the Golden Watch is in Customs. Place was dead, no sounds no others.

I kept the volume up just incase but continued talking on the phone. 15 minutes later. All of sudden I'm being shot in the back by a PPSH. I go to chase the guy and he disappears, so I flank around the container where my back is up against the wall, only place for him to push me would be directly in front of me, well he just knows exactly where I am, while making zero foot steps and shoots me through the shipping contains doors and boom head/eyes.

I find it funny that everytime I'm wearing good gear all of a sudden people are doing WANTED movie shit and shooting around or through corners, but if I go in with some slop ass kit no one cares and I rarely but into anyone.

The cheating is beyond levels it was at even when Wiggle that killed Tarkov happened. Its fucking pathetic and BSG has done literally nothing other than update BE since that video, which is over 2 years old btw.

Cheating is literally what makes me quit everytime I pick this game back up again. It beyond sad that no one (devs) give a shit about this because they make money from cheaters rebuying accounts ever banwave.

Literally ruined Red for me. In the OG series he is already a battleharden badass that took over the tribe from his father that also died in a bad ass way.

Than... you get this little girly boy kid version of Red in Rebirth? Na Fam!

Insert child like voice from Red that made me cringe so hard I literally stripped Red of his gear and material and removed him from my group after this...

https://preview.redd.it/l7v0jkbv3qdh1.png?width=1036&format=png&auto=webp&s=65c25a6fb569afa140095e7377c5ba5a110919cd

Maybe someone can help me with this.

I've been struggling for awhile to make this work as I require. The issue is action sounds, explosions, fight scenes etc... are all way to loud and often voices can also seem softer than they should be.

I have a Samsung Smart TV but using ONN 4k Plus for my Streamining needs. I have the ONN plugged into the back of the receiver.

I can get 5.1 and everything works but I have those audio issues. I tried tons of different options and presets but nothing seems to really resolve the issue. From my understanding this unit has both ALC and Midnight modes as well.

I tried using ALC mode but it forces everything into 2 channel mode so only 2 speaker work. I tried everything I can think of and can't get it out of 2 channel mode while using ALC. From what I read it has something to do with ONN device?

So I disabled ALC and restored my 5.1 channel mode, now all speakers work but again original issues still exist.

I tried midnight mode and testing different presets to see what would work best. So far I got it to a point where action sounds and voices are barely at an acceptable place but now MUSIC is overblown and beyond loud....

I understand there are newer better receivers like a Denon that has built in audio leveling controls but I'd like to avoid having to purchase that if possible.

Any experts in here but any ideas how to obtain what I would like to do with my existing receiver? Again it has Midnight mode and ALC modes but each one has their issues and I cant get ALC to work with 5.1.

Any ideas?

I find it funny Linux community is giving shit to Microsoft for using AI for some of its code while its literally happening to Linux as well. Listen to first 2 minutes of this video.

Linux is also subject to heavy AI coding in the kernel leading to tons of issues being found and having to be patched after the fact.

https://www.reddit.com/r/linux_gaming/s/urrMQiA8xk

So I've been using waveapps for bookkeeping and invoicing for the last 5 years straight. Everything was fine until 2 years ago I moved to an S Corp and needed to add payroll services to my account.

Well, as luck would have it I moved to waveapps payroll a few months before the payroll disaster happened with waveapps in 2025... causing issues with payrolls services, missed payments to IRS etc... for 1,000s of waveapps customers...

Well, I jumped ship and moved to Gusto in the end of 2025 and its been great ever since.

HOWEVER, I received a letter from the IRS stating my 2025 Q2 IRS payments are overdue because Waveapps didn't actually make the payment. I checked my bank statement and of course in July they did pull out $455.75 from my bank to make the payment to the IRS but never made the payment. I contacted support (which is only done from email and takes weeks to months to receive replies) uploaded my bank statement and IRS letter asking for a refund since I had to make the payment manually, but they did take the money out from the account.

Well 2 months later, they did an "investigation" they stated they sent out a letter that the responsibility was on ME to make the payment to the IRS due to the internal issues they were having when they changed processors, and I can confirm I did receive a letter HOWEVER they still pulled the funds out of my account that month so I assumed this was sent in error and let them handle it. Fine, not a big deal the fines from IRS on that was like $10. I'll eat that cost.

BUT THEY STILL TOOK $455.75 OUT FROM MY ACCOUNT THAT MONTH AND DID NOT PAY THE IRS AND NOW THEY REFUSE TO REFUND ME THAT AMOUNT THEY TOOK!

I'm so over the bad service Waveapps provides even for paying customers. I was literally paying for payroll services and this is the treatment we get, bad support, piss poor payment processing for payroll services, the list goes on. Dont support this company, there are a few better alternatives out there for both bookkeeping and payroll services. Save yourselves and use those services instead.

Putting this solution out there as it was a pain for me to figure out it and get it working properly. If you are receiving the above error. It could mean multiple things. Do the recommended troubleshooting 1st before moving to this fix. (google search for bootrec fixes, start up repair etc...)

This is the actual fix which involves replacing the EFI partitions GUID to the correct one that Windows can see and know where is the boot EFI records are.

1. MBR vs GPT Partitions:

First thing to do is check if your boot records and disk is set to GPT. Open Disk Management, select the disk you are troubleshooting with, right click >Properties>Volumes. It should say "Partition Style GPT" if it does. Go ahead and move to Step# 5, if it says MBR continue through all steps in order.

>Notes:
A lot of newer systems dont even allow MBR anymore and/or UEFI bios with GPT\EFI partition booting. So if you ever cloned a system or recreated the EFI partition or running in MBR CMS\Mixed booting mode, this is most likely where your issues start and we need to convert it over.

2. Converting MBR to GPT:

Use a functional system with a USB Dock or Disk Enclosure and plug in the disk we are having issues with. (you can also use a Windows Recovery bootable iso, or a Recuse disk from programs like DiskGenius or Macrium Reflect) but for this we are assuming its plugged into a secondary functional system via a USB dock.

Now install Disk Genius. Open Disk Genius and select the disk we are working with (we will call this disk#5). Verify it states "Partition Table Style MBR"

Right click on Disk#5 and "Convert to GUID" This will convert the whole disk from MBR to GPT style.

Hit "Save All" to commit the changes and we are done here.

3. Fixing Boot Partition Files:

Now because the boot partition still has MBR files on it, it wont be bootable at this point. We need to delete the MBR partition, recreate it and copy over EFI files. This is how we are going to do it.

This can be done with CLI or Disk Management. I'm going to explain how to do it in Disk Management to make it simpler.

Open Disk Management, find Disk #5. Find the MBR partition (typically the "reserved unlabeled partition roughly round 100mb-500mb in size) and delete it. Make sure NOT to delete the partition that contains Windows and your data. Only the MBR\boot partition!

>Note: If you have multiple reserved partitions. Feel free to delete them all since we are recreating a fresh one now.

Now right click the unallocated space we just made, create new Fat32 partition, label it "EFI" and feel free to assign a drive letter. Here we are going to call it drive letter S:

4. Rebuilding EFI Boot Records:

Next is to rebuild/copy EFI files from the existing installation to EFI partition using this CMD command:

bcdboot J:\Windows /s S: /f UEFI

>Note: This assumes your Windows Partition on disk we are working on is drive Letter J: and the EFI Partition is S: Replace with your drive letters if need be.

Done. Now MBR has been converted to GPT. This should allow you to boot back into Windows but you will still receiving error 8x80070003 - 0x40008 when trying to apply the update/upgrade to Windows 11, so continue with step 5 before reinstalling the disk into your other system.

5. Now continue to resolve 8x80070003 - 0x40008 error:

Go back into DiskPart

Select Disk 5 (disk with OS we are working on)
Select Part 1 (newly recreated EFI partition)

Run the following command:

set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override

This changes the EFI partition GUID to something that is findable by Windows subsystems.

Install the disk back into the original PC. It should now boot properly and allow for you to continue with the upgrade/update that was previously failing!

Important Notes:

• Before doing any of this make sure you have a VALID BACKUP of your disk so you can revert back if need be. I personally cloned my original hard drive and did this all on the cloned disk, than once it was working I replaced my original disk with the cloned one. This makes it way easier to deal with instead of having to restore from a backup if things fail.

• The reason we HAVE TO convert to GPT is because the command "set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override" only works with GPT style disks. If its not a GPT style disk you will run into an execution error when you try to run the command.

• Thirdly yes this GUID fix is the resolution to this issue. Why does it work? Well it converts the existing GUID into one that Windows understands by default and can easily find. Its mostly used for things like Firmware and Windows Upgrades. This explains why your old disk may still be "bootable" but not "upgradable". As the boot process doesnt really care about GUIDs but for upgrades and firmware do care!

• If you can't boot after doing this. Make sure your bios boot is changed from MBR to GPT mode. AKA Legacy boot to UEFI.

And last but not least. This whole process assumes you are not dual booting on the disk we are working on. That is a process might be different and you may have more reserved partitions that if deleted could break your dual booting. So be careful with that and know what partitions you are deleting before you delete them!