[SOLVED] Net Framework 3.5 cant modify and random shutdown

mobostar0101 · Oct 16, 2024

Hi,

I recently sent SFCFix.exe for repair via DISM and everything went well, it passed 100% successfully.
Windows Update is updating normally after the fix, but after a while of use the system appears with a touchscreen shutdown warning and turns off, this happens sometimes and I don't have a touchscreen...I believe this a system file issue...
I get error 0x80070002 and the Framework won't uninstall.
I ran DISM and SFC, but the error persists.

please how to fix this error?

x BlueRobot · Oct 17, 2024

Please follow the posting instructions as you have done before: Windows Update Forum Posting Instructions

mobostar0101 · Oct 17, 2024

the files is attached.
ps.: the CbsPersist.log is too large even though it's text

I compress as niemiro wrote

x BlueRobot · Oct 17, 2024

Code:

2024-10-16 16:24:15, Error                 SXS    Could not open \SystemRoot\WinSxS\Manifests\amd64_b6afaf75dff894c376ec9a7e6e15e49f_b03f5f7f11d50a3a_10.0.22621.615_none_de1645d7d008e71c.manifest: STATUS_OBJECT_NAME_NOT_FOUND
2024-10-16 16:24:15, Error                 SXS    WIL Origination: onecore\base\servicing\turbostack\lib\turbostackutil.cpp(70)\TurboStack.dll!00007FFAFBA938FB: (caller: 00007FFAFBA93CA1) Exception(1) tid(2cdc) C0000034 Nome de objeto n\u00e3o localizado.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or WeTransfer and then just provide the link in your reply.

You may be able to zip up the file and then attach to your post; the attachment limit should be 100MB.

mobostar0101 · Oct 17, 2024

I think attached here, the .zip file have only 14mb

x BlueRobot · Oct 17, 2024

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please try and modify the .NET Framework 3.5 feature again and let me know if it fails or not.

mobostar0101 · Oct 17, 2024

I apply the FIX, this copy the files but the error 0x80070002 persist and the Framework won't uninstall.

x BlueRobot · Oct 17, 2024

Okay, please provide the latest CBS log(s) as you've done before.

mobostar0101 · Oct 17, 2024

I try reboot and run SFC, but Framework won't uninstall.

attached the CBS files.

x BlueRobot · Oct 17, 2024

mobostar0101 said:
I try reboot and run SFC, but Framework won't uninstall.

That's because you still have corrupt/missing .manifest files associated to .NET Framework 3.5.

Code:

2024-10-17 11:04:32, Error                 CSI    0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #664067# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0xa03befa730->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[118]'\??\C:\WINDOWS\WinSxS\Manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_10.0.22621.615_none_a650922862552ca9.manifest'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa03befa918, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHA[gle=0xd0000034]
2024-10-17 11:04:32, Error                 CSI    RE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2024-10-17 11:04:32, Error                 CSI    00000010 (F) STATUS_OBJECT_NAME_NOT_FOUND #664066# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemFile(flags = 0, da = (FILE_GENERIC_READ), fn = [l:115]'\SystemRoot\WinSxS\Manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_10.0.22621.615_none_a650922862552ca9.manifest', sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)

Please follow the same instructions as before but use the attached SFCFix.zip, it will fix the missing/corrupt .manifest file shown above.

x BlueRobot · Oct 17, 2024

If you still can't uninstall .NET Framework 3.5, then please download the .zip, extract the .ps1 file and then run the script from an elevated PowerShell window. Please post the output in your next post.

You'll need to ensure that the COMPONENTS hive is loaded beforehand though, using:

Code:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

mobostar0101 · Oct 17, 2024

I run the FIX and the problem to uninstall Framework persist.
I cant run the content ps_script.zip, the file manifests.ps1, I got this error:

Code:

manifests.ps1 : O termo 'manifests.ps1' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa
operável. Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente
novamente.
No linha:1 caractere:1
+ manifests.ps1
+ ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (manifests.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: O comando manifests.ps1 não foi encontrado, mas existe no local atual. Por padrão, o Windows PowerShell não carrega comandos do local atual. Se você confia nesse comando, digite: ".\manifests.ps1". Consulte "get-help about_Command_Precedence" para obter mais detalhes.

x BlueRobot · Oct 17, 2024

I assume you saved the .ps1 file to your desktop then? If you did, then you would need to use .\manifests.ps1. For the loading of the components hive, you have a typo and used the incorrect file name. It's "COMPONENTS" and not "COMPONENT", please ensure that you double check for any typos.

mobostar0101 · Oct 18, 2024

sorry, I really wrote it wrong... I run the correct name and restart the system, but I got same error 0x80070002, the Framework won't uninstall and the manifests.ps1 dont run.

mobostar0101 · Oct 18, 2024

I run .\manifests.ps1 instead manifests.ps1 and got this

Code:

PS C:\Users\Calibracao.02\desktop> .\manifests.ps1
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_031877d9e94bcfd3fba66dfa3a521f66_b03f5f7f11d50a3a_4.0.15912.322_none_0527195ee6b8b5e7.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_0d86c91edf66e5f5162c25c9c5e780bf_31bf3856ad364e35_4.0.15912.345_none_da60d96b693cd2af.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_0dc8179196c88d3a18a355c1f34a7fed_b03f5f7f11d50a3a_4.0.15912.355_none_504533116ec30518.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_0e35624a13b4c413a7a0a14e2b46cbc7_b03f5f7f11d50a3a_4.0.15912.322_none_dd0a60e191f90aa0.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_0f44b87a719dc4582ade906611ac7ec7_b03f5f7f11d50a3a_4.0.15912.322_none_7d2c28b1d780a8ba.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_13f8b55d6b70837e38288bc4da269f22_31bf3856ad364e35_4.0.15912.345_none_f54cc7b6295b12fd.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_15579e82e69f856aace9db65c90dc10e_b03f5f7f11d50a3a_4.0.15912.305_none_326d36a0b291a5d1.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_1abda078c6ca4b2bfbbe0167dfb7a619_b03f5f7f11d50a3a_10.0.22621.615_none_117f6ff62323f2f5.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_1ed6020a3b3d22d4b2eabeb62960eab6_b03f5f7f11d50a3a_10.0.22621.615_none_b1e65d2f93cbc7e8.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_2186da40eb4dd2c1ed5cad328cff96fb_31bf3856ad364e35_4.0.15912.345_none_7f0f9fe364df66ad.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_26c8f4b6c8d746ca2e8a321593ab3252_31bf3856ad364e35_4.0.15912.345_none_0a00d33035f3a598.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_45c4d71604cd24649a243533746ed379_b03f5f7f11d50a3a_4.0.15912.345_none_ea8decd1a80bed19.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_46467c6e6745c4288831c600a9fb3585_b03f5f7f11d50a3a_4.0.15912.345_none_197b7365a85cd3b7.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_55179c65141a09ef4db2322d062214c5_b03f5f7f11d50a3a_4.0.15912.345_none_b7644c99ed92338d.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_62bd384622b92c6af8f4bd9a5b719aa8_b03f5f7f11d50a3a_4.0.15912.355_none_0fb8e32811308ce2.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_64c614df010cc38ac427f23c5b95ec18_b03f5f7f11d50a3a_4.0.15912.345_none_f7ccb2b026dc0d7e.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_6717ec80258772a330409f4be25c6d3b_31bf3856ad364e35_4.0.15912.355_none_3d6acde6e98743c4.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_6779a0acd432b6244bdab224861d13cb_b03f5f7f11d50a3a_4.0.15912.355_none_d3903505e6903fe6.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_723060ace4a74a2d48d890acbcd9f7f0_b77a5c561934e089_4.0.15912.350_none_e923b6b7450a7f27.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_7355690ec1670766a0d48b7577f7b893_b77a5c561934e089_4.0.15912.345_none_cbcc4a9c4c3d900d.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_76ec8f8911e460bf05bfe42f7bddbf55_b03f5f7f11d50a3a_4.0.15912.355_none_1e5def1e7cea7d1e.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_8a18d106ebcaca34a602d1ee7b6b6484_b03f5f7f11d50a3a_4.0.15912.322_none_11db34d54083948a.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_8f34258d7428a9f6140d47e11506b00c_31bf3856ad364e35_4.0.15912.322_none_757dd555e7abb04a.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_9015a84be438807eccbba6f5b400e0f6_31bf3856ad364e35_4.0.15912.345_none_d159c28acf6e1af8.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_974417a5f48f3a946b39c64407787778_31bf3856ad364e35_4.0.15912.345_none_af03d6aa759617ca.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_a468662267ab90e61136ed53c6eac4fc_b03f5f7f11d50a3a_4.0.15912.322_none_ec5dda3ac220928c.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_ab82c9ab92aa2989502bb67c3e8ce74e_b03f5f7f11d50a3a_4.0.15912.345_none_a5d53d928f5d39c9.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_aedfd7f831436a828294d3b9cea5131c_b77a5c561934e089_4.0.15912.355_none_931fa93cbcd07f0e.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_b1dafe30c52ec843a977abbd8a767bd9_b03f5f7f11d50a3a_4.0.15912.355_none_9f56c975691989e4.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_b76414291acd336116a37bc569d4630f_b03f5f7f11d50a3a_4.0.15912.355_none_6348fa269f414289.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_bb646f1758db0a98d26895043a755ba5_31bf3856ad364e35_4.0.15912.345_none_f05830bef202d653.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_c2538f6b539f680cfff368e3ed3621a5_b77a5c561934e089_10.0.22621.615_none_5d42dc161ea1d3f2.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_cc58bcdd289c4503d2df14100cce252f_b77a5c561934e089_4.0.15912.345_none_e37d397386542cff.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_cd0f54129b491ec1805afe255771084c_b03f5f7f11d50a3a_4.0.15912.345_none_aac5ab8338c4a0e9.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_ce3241a5f4970a7283088315c7c50ba6_b77a5c561934e089_4.0.15912.345_none_01503b00609d39ce.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_d77bb0c6b51c2e2a160bf592e33d4e33_b03f5f7f11d50a3a_4.0.15912.355_none_186e448492fec285.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_e986a8addd62c69aa8e0ddbe6cd6ab89_b03f5f7f11d50a3a_4.0.15912.355_none_837f92622dfff52d.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_ec22f7b909813fd8e93e383bd9b55732_b03f5f7f11d50a3a_4.0.15912.345_none_65e31ed8ce77d021.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_edd9769793133f6b6c4e5f532dd66e41_b03f5f7f11d50a3a_4.0.15912.355_none_4581a9c958637357.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_f1891096d576a0026d3ce46017490bea_b77a5c561934e089_4.0.15912.345_none_7b48b4567c54ffe8.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_f375e70452d7bdbfa8830c9f05830e20_b03f5f7f11d50a3a_4.0.15912.345_none_c91ff9a585e7cc35.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_f4bcb8496e2667f7186243421308e67d_b03f5f7f11d50a3a_4.0.15912.322_none_d46ee2e6d249e9f3.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_faef6b237c78fbf24732f2837b124a33_b03f5f7f11d50a3a_4.0.15912.322_none_ba2a8737f0a5c0e4.manifest could not be found
The .manifest file C:\WINDOWS\WinSxS\Manifests\amd64_fb824f07abb8e670e25ff8b93c6dbcb3_31bf3856ad364e35_4.0.15912.322_none_5f4402a60e0e7c1b.manifest could not be found

x BlueRobot · Oct 18, 2024

Thanks, I'll write a fix script to replace these missing .manifest files for you.

x BlueRobot · Oct 18, 2024

Please follow the same instructions as before but if it fails again, then please attach the latest CBS log(s).

mobostar0101 · Oct 18, 2024

I apply last SFCFix.zip and restart the system, then try uninstall Framework and got same error 0x80070002.

attached the CBS.

x BlueRobot · Oct 18, 2024

It looks like there is still missing .manifest files which are all related to those update packages which fixed in your previous thread. Please try and use the .NET Framework repair tool:

Download the

Microsoft .NET Framework Repair tool and save it to your Desktop.

Right-click on NetFxRepairTool.exe and select Run as Administrator.
Agree with the license terms "I have read and accept the license terms" and click Next.
After checking, the tool will indicate which problems need to be fixed.
Click on Next to continue, when this process is finished click Next.
The tool will now collect the log files... > when completed the following file is created: FixDotNet****.cab.
Click on Finish to close the tool.
Right-click on the file FixDotNet****.cab and choose Send to > Compressed (zipped) folder.
Attach the ZIP file in your next reply.

mobostar0101 · Oct 18, 2024

the .cab is attached.

[SOLVED] Net Framework 3.5 cant modify and random shutdown

Active member

Administrator

Active member

Attachments

Administrator

Active member

Attachments

Administrator

Attachments

Active member

Attachments

Administrator

Active member

Attachments

Administrator

Attachments

Administrator

Attachments

Active member

Administrator

Active member

Active member

Administrator

Administrator

Attachments

Active member

Attachments

Administrator

Active member

Attachments