📎 AI Summary:
The thread discusses a Windows user experiencing issues with the system cleanup process not completing, as it gradually removes files but remains stuck with a humming fan and no success message. Contributors advise letting the cleanup run longer, noting it can take over an hour initially, and suggest it may improve with regular maintenance rather than indicating a faulty OS. The original poster plans to run the cleanup again before imaging the system, concluding that the process is likely normal and not indicative of problems.

Peterr

Essential Member
Joined
Mar 31, 2011
Messages
1,173
Thread Author #1
I used the disc with a generic key to install and my 8 key to activate. All went well but the cleanup system files will not close. It removes bits at a time but the fan is humming and it does not say successful or close. It does chip away so there are a few mbs left.
I was hoping to close so I could image a clean OS with no defects. I ran the health DISM and the win update trouble shooter.

Is this something to attend to before imaging?
 

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Hi Peterr,
is the disk clean app still open? Depending on the specification of the machine used then disk clean can take a while. Your probably better off just letting it do it's thing.
 

Peterr

Essential Member
Joined
Mar 31, 2011
Messages
1,173
Thread Author #3
I will let it run but last time I let it go for about 1/2 hour with the fan humming and it never finished.
Would you image it as it or consider it a faulty OS b/c this feature will not conplete?
 

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Do you mean you left it for 30mins and it didn't finish? I'd leave it longer although what you should find is that the first time around it will take a while perhaps over an hour. If you run the app maybe once a month you'll find that it will speed up as your system will be in better shape with each successive run.
 

Peterr

Essential Member
Joined
Mar 31, 2011
Messages
1,173
Thread Author #5
So it is not faulty - I will give it another run then regardless, image it. Thank you