QuickBooks DESKTOP 2023 will yet AGAIN NOT START

I appreciate you sharing the details and results of the steps you've performed, @Sizzler42. I'll share additional information and steps to resolve this.

The error 1336 in QuickBooks Desktop (QBDT) can be caused by the loss of Windows system files. No worries, I know other ways to help you get rid of this error. We can start the troubleshooting steps by repairing or reinstalling the Microsoft .NET Framework. 

The system uses Microsoft programs to run web-based apps and one of them is Microsoft .NET Framework. If it has an issue, QBDT may not work properly. To fix this, refer to the steps below:

1. Close all open programs and open the Windows Start menu.
2. Next, type Control Panel into the search bar and open Control Panel.
3. Navigate to Programs and Features.
4. Then, select Uninstall a Program (you aren't uninstalling anything).
5. From there, select Turn Windows features on or off.
6. Look for the .NET Framework on the list.

Then, check the settings for both .NET Framework 4.5 (or later) and .NET Framework 3.5 SP1. To proceed, follow the steps in this article: Manually fix Microsoft .NET Framework errors. After that, open the QBDT again.

If the same thing happens, you can consider installing your QBDT on another computer to verify if the issue is related to your device. 

However, if the issue persists, I recommend working with your IT personnel or contacting Microsoft support as there may be damage to your computer's Windows Operating System or the hard drive itself. They can provide steps to help resolve this. 

Should you need additional help or anything you'd like to know about accessing your QuickBooks account, feel free to drop a reply below. I'll be here ready to provide prompt assistance. 

This NET feature?:

Thanks for getting back to us and providing some screenshots, Sizzler42.

Yes, you're right. Verify the settings for it. If the checkbox is not selected, then:

1. Click the checkbox to turn on .NET Framework.
2. Hit OK to save your changes.
3. Restart your computer.

However, if it is already selected:

1. Click the checkbox to turn off the .NET Framework.
2. Select OK to save your changes.
3. Restart your computer.
4. Once signed in, follow the steps above to turn on .NET Framework again.

If you encounter an error while doing the troubleshooting steps, I recommend contacting an IT professional or reaching Microsoft support. There might be damage to your computer's Windows Operating System, and they will be able to assist you in resolving the issue.

Reach out to us if you have any other concerns with QuickBooks. Remember, we're here to make sure everything is taken care of.

Same result.  Here is the log file:

**************insert*********************

trackdll.cpp (148) : MESSAGE: 5352: Mon Sep 25 07:51:48 LVL_SEVERE_ERROR--MainFrame must be already created by now as this dll is demand loaded
qbwindll.c (115) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 CQBWinApp::InitInstance -- Initializing QBWinInstance Handle
qbwindll.c (146) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 CQBWinApp::InitInstance completed
qbw.c (2154) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: Entered
qbw.c (2159) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: AquireLock() -ok
qbw.c (2173) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: After FileRedirectInit()
qbw.c (2209) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: Before CreateMutex- Global\Intuit, Inc. QuickBooks.
qbw.c (2211) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: After CreateMutex- Global\Intuit, Inc. QuickBooks.
qbw.c (2238) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: After CreateMutex-
qbw.c (2248) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: After FindWindow - MauiFrame
qbw.c (2258) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: before CheckFlavor
licenseutility.cpp (1832) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Initializing QBLicense Adapter for version 33 and flavor pro, which will initialize .NET EC if in Handshake Mode
licenseutility.cpp (1832) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Initializing QBLicense Adapter for version 33 and flavor pro, which will initialize .NET EC if in Handshake Mode
qbw.c (2260) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: after CheckFlavor
qbw.c (2291) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: After - MIData.IsMyInstanceRestricted
qbw.c (2373) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: before - Test for adequate memory the first time through
qbw.c (2408) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: Before test to Make sure that we're on a VGA. (only for first instance)
qbw.c (2419) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: before SwitchToQBWDir
qbw.c (2421) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: after SwitchToQBWDir
qbw.c (2522) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBWMain: Before AfxWinMain
qbw.c (318) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 CQuickBooksApp::InitInstance Initializing Quickbooks (AfxOLE)
LEDXMLReader.cpp (157) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 LED: LEDConfigFile was either not found or is corrupted
qbw.c (322) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Operations Started
qbw.c (545) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Multiple Instance - Attempting to opening file ><
qbw.c (764) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Multiple Instance - Opening file(done) ><
qbw.c (929) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 Calling MauiMain for further initialization
TLSMigration.cpp (373) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 ValidateTLS12Support - Inside ValidateTLS12Support function
TLSMigration.cpp (376) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 ValidateTLS12Support : Executing Hard Coded TLS 1.2 support.
qbbrowse.cpp (5089) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 GetIEVersion IEExplorer version = "HKLM\SOFTWARE\Microsoft\Internet Explorer\svcVersion" , returned 11.789.19041.0
fileutils.cpp (660) : CHECKPOINT: 5352: Mon Sep 25 07:51:48 QBUpdateMonitorService service starting...
dbmanager.cpp (4295) : CHECKPOINT: 5352: Mon Sep 25 07:51:50 ServerNameBuilt: ServerName:QB_DESKTOP-LHHBM7F_33, MachineName:DESKTOP-LHHBM7F, EngineName:DESKTOP-LHHBM7F
dbmanager.cpp (4295) : CHECKPOINT: 5352: Mon Sep 25 07:51:50 ServerNameBuilt: ServerName:QB_DESKTOP-LHHBM7F_33, MachineName:DESKTOP-LHHBM7F, EngineName:DESKTOP-LHHBM7F
dbmanager.cpp (4295) : CHECKPOINT: 5352: Mon Sep 25 07:51:50 ServerNameBuilt: ServerName:QB_DESKTOP-LHHBM7F_33, MachineName:DESKTOP-LHHBM7F, EngineName:DESKTOP-LHHBM7F
dbmanager.cpp (4295) : CHECKPOINT: 5352: Mon Sep 25 07:51:50 ServerNameBuilt: ServerName:QB_DESKTOP-LHHBM7F_33, MachineName:DESKTOP-LHHBM7F, EngineName:DESKTOP-LHHBM7F
dbmanager.cpp (2410) : CHECKPOINT: 5352: Mon Sep 25 07:51:50 QBCFMonitorService service starting...
KillSwitchHelper.cpp (117) : CHECKPOINT: 5352: Mon Sep 25 07:51:51 IsFeatureEnabledInIni: Value read from ini file from DTMStandAloneTool :: IsEnabled is -1
mainfrm.cpp (894) : CHECKPOINT: 5352: Mon Sep 25 07:51:51 CMainFrame::AddDomainAndIconBar
mainfrm.cpp (1177) : CHECKPOINT: 5352: Mon Sep 25 07:51:51 Quickstart - reached [1]
performancemeasure.cpp (1055) : CHECKPOINT: 5352: Mon Sep 25 07:51:51 LARGEADDRESSAWARE is on!; # of processors:4

@Sizzler42 

You are using QBD 2023 Pro or Premier, correct?

Install the trial version of QBD 2023 Enterprise. Did you encounter the same problem?

I share your frustrations.  I have spent several hours every month fighting with QB 2023 Desktop Accountants Edition.  Although they claim they are not phasing out QB Desktop - they are making it very difficult to access and or consistently use. First, the pointed advertising that leads people to believe the only options are QB Desktop Business Essentials or QB Online - and that is from not only the website but also clicking the link for renewal in the Desktop software.  The only place to buy the software now is to go directly thru Intuit.  That call and/or chat session will involve up to 4 different transfers, all trying to extoll the greatness of QB Online.  You have to tell each one that you DO NOT want the online version, then finally they will give you the price, but you have to pay through the link they send you.  Then, when you are finally able to use the software, it has become very glitchy.  I am sure I am not the only one to notice the repeat threads of the same complaints - most of which directs people to use the QB Tool Hub.  I have regretted upgrading my company file to the 2023 version, and like several others am after 20+ years beginning to look elsewhere for software.  

@Amy P 

he only place to buy the software now is to go directly thru Intuit.

You can purchase new or renewal licenses through selected partners, especially if you want to avoid using your own credit card. If you don't need to manage payroll with QB Desktop Payroll, you can use the trial version of QB Desktop for good if required.

QBDT 2023 Pro.  Just spent 25 hours troubleshooting only to have to do a fresh install in a new W10 account.  Luckily I had back-ups.  But here is what I did:I essentially gave up and did a fresh install

I could not uninstall (Error 1226), I could not upgrade (Error 1336), I could not launch as administrator (Just disappeared).  When I sanitize my Chat session, I'll post it here