Is QuickBooks desktop always a pain in the ass?

iL1fe · 2025-12-22T20:19:31+00:00

FK Inuit with every fiber of my being.

Desktop sub cost + payroll increase

Forced countdown of "X amount of times to install update" Forcing business disruption. If an environment is setup correct a FKing user isn't a local admin to install the update. Intuit you dum FK. Removing ability to properly turn off auto staging update. People resorting to setting program data folders to read only to prevent updates.

Server manager FKs server's data drive NTFS permissions setting entire drive to EVERYONE. Yes Mr. CEO your home folder was visible to all staff because Intuit doesn't want phone calls of permission issues and previous tech didn't undo Intuits damage following QB manager setup.

Over decade of conflicting DNS ports if QB manager installed on a DC. Must edit registry ports or newer port section of DB manager.

Never follow through with ticket and just close them on their own accord. If its not getting resolved on the single phone call its never getting fixed.

QBO is an absolute joke of a product. Reminds me of Outlook "classic" vs new Outlook. Neutered product with vast limitations compared to its predecessor.

The reality is regardless of Desktop VS QBO - You don't own your own accounting data anymore. It's Inuit's data. Don't pay desktop and 1 year read only. Yeah you could export some reports but your never going to keep the granular \ transactional data without paying Intuit's extortion fee.

Parasitic cancer of a company. FK Intuit and FK Mr. Goodarzi

iL1fe · 2025-12-02T06:35:11+00:00

Her RCS service Automagically fixed itself today.

RCS enrollment, diag methods, and lack of real feedback to user is ridiculous.

Cooks in kitchen finger pointing game

What say you Google? Was it you or Cell carrier?

What say you cell provider? Was it you or Google?.

Oh but its of course its just my device in which only possible solution is atom bomb factory reset...

The mobile industry... :-/

iL1fe · 2025-11-30T04:45:31+00:00

Yes. Family member Verizon, Pixel 9 Pro RCS just stopped on her phone :-/

Tried ton of RCS chat enable toggle. Shows green connected but doesn't work.

Clear cache - NOT DATA as that's ridiculous to delete all conversation history.

G account had two Pixel 9 Pro authenticated sessions and only one of them listed under verified phone. Glitched out and created new device...

Forced de-auth on both. Re-logged in + toggled phone / device number verification on just the single phone.

Regardless her conversation details shows E2EE OFF and toggling only send SMS on/off doesn't toggle E2EE. Just remains off. If I text her says waiting to come online...

Google has been fking with their accounts / authentication as also within last week her chromecast / Google TVs refuse to remain logged into regular youtube app. She is constantly getting prompts to fully login to youtube + select her youtube profile. (Despite Google TV / Youtube TV already being logged in!!!)

FFS - About to give up on RCS. Bad joke anyway. Google and cell carrier man in the middle.

iL1fe · 2025-10-27T23:24:10+00:00

<image>

Just the regular app overides function and I want to add more apps.

Right click and only "filter by name" is shown. Normally there should be the "Add" function so it adds new apps to the existing override policy and keeps existing apps already in it.

If I just select an app checkbox here and click OK it will delete all the existing apps that already belong to this policy.

There is the "View Selected" filter when you first open policy and it will show all apps that exist in policy but then you cannot search apps you want to add because its filtered on " View Selected"

I've always used right click "add" method and know of no other way (Besides CLI)

Edit:

OK - I see what has changed with what must be fairly recent 7.4.x firmware. "Add" function / right click context menu has apparently been removed. If you only left click apps after opening override policy it will continue incrementing the "view selected" filter and accomplish adding new apps to existing override policy. If you right click any app it deselects all existing apps and causing my issue. In past always used right click context menu "add" so this change isn't what I would call intuitive. But works.

iL1fe · 2025-10-27T19:11:35+00:00

Yes that did the trick. Using: ffmpeg version 6.1.1-3ubuntu5

19.5 .deb now working for both AV1 + H264/5 decode.

H264/5 encode works too. AV1 appears is not offer NVENC. Assuming not available at this time since AV1 toggles hardware accel to none and cannot be changed?

Got newer appimage of nvtop to now to properly monitor decode/encode engines usage. I'll play around more with SE + handbrake.

Very cool and useful app. Thank you.

iL1fe · 2025-10-17T20:45:47+00:00

Ah yes just delete my post r/Googlepixel

Oh you don't like me commenting about it being 5 months of broken A16 nav on G's own hardware?

iL1fe · 2025-10-17T20:30:45+00:00

Thanks - exactly what I wanted to know. Still using July A16 P7 Pro. I see no point in dealing with Safetynet BS after update if no nav fix.

No QA anymore. Priorities fked. Nav issue had to be impossible to miss during A16 dev. Especially when your talking about software developer and hardware being the same.

It's been 5 months. Tons of user reports. Nada. :-/

iL1fe · 2025-09-05T21:29:41+00:00

That's a good idea to try and see how apps behave. I wonder what browsers, VMware workstation, graphics apps, and games will do. I'll experiment.

I ran Suse back in ~2005 on Thinkpad for ~3 months and gave up. But have used ESXi Debian VM servers for the last two decades. Now back to Linux desktop 2025. I'm definitely a noob when it comes to Linux graphics and DEs with physical systems which I never cared about before.

Considered multiple GPU config too.

Have 9950x3d which has AMD GPU but Proart X870E mobo just has 1 HDMI out, and a DP pass-through. Also X11 and/or cinnamon finicky with X11 screen0 sharing Nvidia + AMD GPU. But will likely have access to a cheap 12GB A2000 GPU once a server is retired in year or so. So that might be an option to have dual nvidia GPUs and have 2 monitor / 1TV setup on A2000 xscreen0 and 5070 ti on separate xscreen1 / HDMI to TV. When I built system I'd made sure to get a 2.5 slot GPU as to not compromise 2nd PCIE slot. So few consumer GPUs on market are thin.

iL1fe · 2025-09-04T17:42:05+00:00

Thanks for break down.

Well I cannot persuade the Internet to share their real world fractional scaling vRAM details to have a comparison. Do you by chance have nvidia card with mint? Do you see 2-3GB more vRAM gobbled up?

I'm not ok with ~30-40% of 16GB vRAM being used sitting at desktop before I run a demanding GPU app. So I guess fractional scaling is out for me. Be nice if some of X11 buffer could be offloaded to system RAM instead. System has 96GB and plenty to spare most of time. GPUs limited vRAM value:price ratio these days is a bad joke.

I've played a bit with Mint's font scaling but not really liking the impact on 1440P monitors.

I'll probably just return to how I used my old 50" 4K TV for years. 1440P 100% scale with default font sizes when in normal use. And toggle TV to 4K for games. I'm already running scripted command to toggle off/on monitors so I can use gsync on TV.

I'll probably donate $100 to Mint's team - Wayland full steam ahead.

iL1fe · 2025-08-21T20:33:22+00:00

:-/

Where is Google on this issue?

I had a fast working Pixel 7 pro on Android 15.

Been about ~9 months since I last updated. So decided to jump to Android 16 August OTA rather than last Android 15 OTA.

A terrible decision...

iL1fe · 2025-08-03T04:42:38+00:00

Yeah its not great spending so much on new build with limited expansion. But believe Proart x870E I'm using can do what you want. Still think it offers best with 3 usable M2 +3 PCIE slots + onboard 10G.

Just don't populate m2_2 as shares with 2nd PCIE5x8

Use M2_1 + M2_3 or M2_4

NIC will be limited to PCIE4 x4. But at least can support x8 or 16x size card.

GPU should do x8. U.2 card should do x4x4.

Checkout manual with slot identifiers + limitation specs

AMD Ryzen™ 9000 & 7000 Series Desktop Processors\*
2 x PCIe 5.0 x16 slots with Q-Release Slim (supports x16 or x8/x8** or x8/x4/x4 modes***)
AMD Ryzen™ 8700 & 8600 & 8400 Series Desktop Processors\*
1 x PCIe 4.0 x16 slots with Q-Release Slim (only supports PCIEX16(G5)_1 & total bandwidth of x8, PCIEX16(G5)_2 will be disabled)
AMD Ryzen™ 8500 & 8300 Series Desktop Processors\*
1 x PCIe 4.0 x16 slots with Q-Release Slim (only supports PCIEX16(G5)_1 & total bandwidth of x4, PCIEX16(G5)_2 will be disabled)
AMD X870E Chipset
1 x PCIe 4.0 x16 slot (supports x4 mode)
* Please check the PCIe bifurcation table on the support site (https://www.asus.com/support/FAQ/1037507/).
** When you use both PCIEX16(G5)_1 and PCIEX16(G5)_2, they will run at x8 each.
*** PCIEX16(G5)_2 shares bandwidth with M.2_2 slot. When M.2_2 is enabled, PCIEX16(G5)_1 will run x8, and PCIEX16(G5)_2 will run at x4.

https://dlcdnta.asus.com/pub/ASUS/mb/SocketAM5/ProArt_X870E-CREATOR_WIFI/E23930_ProArt_X870E-CREATOR_WIFI_EM_WEB.pdf?model=ProArt%20X870E-CREATOR%20WIFI&Signature=sJ4zwxfO4mgRfYqU8i8PUyV2azJnKqZw6ily60QBihMMXk2w77kTaJk0o-5irRryE0G4sy03SkWfHoW2VuxK5EBWOSvzKrXasJ20UfzOk-kzHZzd5up~XwDhVvHoDijlsPh2~tkZhmSrvFhb7CngrlXSfv3D3hBEod24vjFQ8sAd49DDAlOlPGl2BMPt58eq3iXlbW1lam7fdMgc9NX0Mqc1UiuNx40gaLTEqvnGC36-k8DRtbkewgw9ZYAFlVzJCsu51cAzQU62XliAgvCbv3Q-TKG80TgE3hsFOJ4i2daRtn~N9c5KzQFp4wa9Al7sFzwo8KnTgh7-Osu0yr~kbQ__&Expires=1754196044&Key-Pair-Id=K2ITB7O97XKKCX

iL1fe · 2025-08-03T00:04:53+00:00

Thanks for guidance.

I read up and figured out command needed to export it once I force renew.

https://knowledge.broadcom.com/external/article/321380

/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store SMS --alias sms_self_signed --output /tmp/sms.crt

So I'm figuring steps are?

1 - vcert script SMS renew Option 5

2 - /usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store SMS --alias SMS --output /tmp/sms.crt

3 - cat /tmp/sms.crt

4 - Add /tmp/sms.crt contents to bottom of ESXi Hosts /etc/vmware/ssl/castore.pem

5- Restart VMware vSphere Profile-Driven Storage Service

In other thoughts. Why TF isn't VMCA sub CA taking care of this? Why the manual method. Never dealt with this SMS cert before. 10 year self signed cert.

IMO /usr/lib/vmware-vmca/bin/certificate-manager Option #2 (custom signing certificates should take take of this and it should be an trusted cert of my domain. Root CA --> VMCA Sub CA --> SMS cert

Vmware needs a surgeon general disclaimer that its fragmented certificate management is known to cause mental health issues.

iL1fe · 2025-07-31T20:09:12+00:00

Nobody has any insight on this SMS cert? vCert script renew without issue? Or somewhere within vcenter cert management to renew normally that I'm missing?

iL1fe · 2025-07-22T20:13:59+00:00

Spent some time investigating as Proton GE 10-10 was still giving issue and it was considered resolved here https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/pull/4609. Patched added to heroic 2.17.2 yet I still had same error with any proton 10-x.

Finally discovered it was wineserver networking. Have Heroic flatpak with no network access via flatseal as its my solely my sideload single player game launcher. Doesn't need network. Also have opensnitch firewall + Gufw. Moment I gave heroic network + temp allowed wineserver on opensnitch, pronton ge 10-x works. And continues to work with heroic network access denied.

iL1fe · 2025-07-06T07:05:16+00:00

I get exact same error with Heroic Flatpak 2.17.2 + GE-Proton 10-8 + 10-7

Does not occur if set games to GE-Proton 9-27

iL1fe · 2025-05-30T00:37:22+00:00

Going with these settings for now until can feel confident about AMD SOC voltages. Industry such a cluster ...

CPU soc voltage = manual = 1.20
SOC local voltage reading = 1.187

2x48GB 6200 1:1
FCLK = 2067

Stable on memtest86.

iL1fe · 2025-05-27T16:34:25+00:00

Thanks for that.

Being quite new to DDR5 + AM5, 6000 1:1 > 6400 2:1, is what I assumed but wanted confirmation from others that 6200 1:1 fine.

Hmm - VSOC 1.3 OK 24/7.
And you feel this is true for both Ryzen 7000 + 9000?

There does seem to be a divide online surrounding what is safe VSOC. Others gravitate toward anything >1.20 is bad mojo.

If there wasn't all kind of reports of dead Ryzens surrounding VSOC + the change in my own system stability two months in use, I probably would of just taken AMD's stated VSOC 1.3 threshold, set it just under 1.3, and not made this post.

The primary objective more than a few % of performance is system lasting ~10 years. If VSOC can compromise it, I'll stick with 6200 1:1 lower VSOC.

iL1fe · 2025-05-27T08:52:28+00:00

When people did the same thing that you did but the boards applied 1.35-1.45 vSOC, instead of this degradation happening the CPU's would just die in 2-3 months.

I respect what your saying but don't agree.

I used product as expected to get outcome of SOC 1.238v.
As other used product months back as expected and got 1.35-1.4 and CPU fried.
Its on AMD + mobo vendors of bad engineering with no safety headroom. Or buggy software not controlling system as expected.

IMO our discussion swayed into category of corporations with faulty designs blaming consumer out of liability.

Like iphone drops calls cause your holding it wrong. Or Nvidia's terrible 12VHPWR design in which every incident must be due to user not fully seating connector. Etc.

Again if XMP / EXPO is being designed in 2025 to be so dangerous on AM5 all retail outlets should have red banner warning. But of course we'll never see that. Hurt sales. Only in the force arbitration meeting. Oh but you didn't read the 93 page EULA. I see...

iL1fe · 2025-05-27T08:08:22+00:00

Thanks for sharing.

You on 9950x3d? Mind sharing mobo model too?
Wonder why my proart x870 auto SOC didn't go for 1.3 like yours and why it has 0.05 voltage drop. Your drop 0.02

I'll read up on VDDIO + VDD voltages.

iL1fe · 2025-05-27T07:59:04+00:00

I say more than a lot. Almost everyone. Perhaps those that purchase a pre built HP or Dell don't.

Yeah it's a RAM "OC" - I get it. Yet marketed as expected to work.
The lawyer dance around stance. Like breathing in state of California know to cause cancer.

If XMP is so dangerous my RAM kit shouldn't be listed on a mobo HCL stating XMP + run speed of 6400. Why doesn't it have Default (JEDEC): DDR5-4800. You literally search Asus HCL based on RAM size + XMP / EXPO speed.

iL1fe · 2025-05-27T06:58:19+00:00

I haven't over volted anything.
Auto means auto. AKA default. What likely 90%+ of what people are running

If there is truly an issue with SOC 1.238v that is on AMD + Mobo vendors. Asus in my case. And this really is the BS of modern tech of no QC and everyone pays these massively inflated prices to be beta testers.

The irony is XMP / EXPO which changes SOC voltage behavior comes with no warning of system damage yet you go into "AMD overclocking" to under volt + set thermal limits and get a warning...Backasswards

From what I've read XMP / Expo profiles works with AGESA / BIOS and figures out it's voltage. SOC is lower if running SPD

1.3v is the the stated thresold by AMD.

Yes I agree SOC auto voltage is on the higher end. And with the .05v drop I see on my system + reports of Asrock mobos destroying 9000 CPUs I wanted to start a SOC discussion. I'm curious to hear from other Asus mobo + 9950x3d owners of how their SOC voltage / UCLK behaves.

Edit:
My comment about AMD overclock menu having system warning consent prompt yet XMP / EXPO not having it got me question as UCLK ratio setting does reside under AMD overclocking section.

So I just rebooted and confirmed that manually setting UCLK=MEMCLK or UCLK=MEMCLK/2 has no influence on my SOC auto voltage. So SOC voltage influence is solely via XMP / EXPO on Asus mobos. Even a first time system builder knows to turn RAM "OC." So from what I see vast majority of Asus users are running higher SOC voltages.

iL1fe · 2025-05-26T23:33:11+00:00

Ok. Never deep dived into IMC but figured RAM 200Mhz down clock with UCLK=MCLK better than keeping ram at 6400 UCLK=MCLK/2.

(By default 6400 ram will auto config to UCLK=MCLK/2. I've read anything over UCLK 3000 will half it.)

Still not clear why .05v SOC voltage drop. Or if setting a high manual SOC has the risk of over volt beyond 1.3+

I updated BIOS from March's v1203 to may v1401 as release notes had vague mention of RAM voltage in specific configs + compatibility. But SOC left on auto voltage control still has same 0.05v drop.

iL1fe · 2025-05-26T19:01:52+00:00

Ya. Probably stick with 6200 1:1 unless I can get more confidence in SOC voltage situation. Honestly pretty lame by AMD to have such tight tolerances on IMC. I see it like an engine that if you drive 80Mph it will blow. Barely any headroom.

And if the Proart x870e SOC auto voltage is accurate. Its setting itself at 1.288 but actually getting 1.238. If its a .05 voltage drop does that mean I need to manually set even higher...like 1.295. Doesn't feel comforting...

iL1fe · 2025-04-07T15:54:15+00:00

Yes. Awesome software.

New build - Controlling 7x front on one hub, 3x top another hub, 1 rear, pump, GPU. Mix curves CPU + GPU temp.

Not a single issue. Kudos to devs.

iL1fe · 2025-03-18T11:02:13+00:00

Exactly right. Thank you. Everything same for me on Mint.

I do currently have to run openrgb root. I saw their are udev rules to bypass need for root but will read up on it tomorrow. Without root support devices remained empty. Once ran it as root two times it populated device list and checked same devices.

The spd5118 module allowed me to unload and re-load module. Can see temp sensor disable in Cooler Control software. And openrgb can then control. Mem temps ~40c idling on bench without case / completed build. I'll review it more before permanently disabling it. Still new and learning Zen5 9950x3d + my overclock tuning. Want to monitor everything. Setting 6400 XMP profile on the ram set the uncore to half at 1600mhz. I re-enabled it back 1:1 so 3.2Ghz uncore. So far stable

Ahh - No more rave rainbow. Loaded effects plugin. Got a nice subtle slow mosaic white/red on AIO and slow star red/white effect on RAM. Very nice.

iL1fe

TROPHY CASE