Forever to Wake Up

[Malnutrition]

I don’t understand what te rest of te post is for. Where am I to post these codes?

Never mind that, just run the batch file and let me know if it works as intended?

Also, since I ran rename many of my keys are not consistently working, particularly H, ', and Backspace. Coincidence?

I ran rename as admin, nothing observable happened.

That would have nothing to do with your keyboard, as your H button was working fine right after as evident in this post you made.

It only renamed Searchapp.exe

You can rename it back if you wish, but like I said this has nothing to do with a keyboard,
@echo off
takeown /f “c:\windows\systemapps\microsoft.windows.search_cw 5n1h2txyewy\searchapp.bak”
icacls “c:\windows\systemapps\microsoft.windows.search_cw 5n1h2txyewy\searchapp.bak” /grant Everyone:F
taskkill /F /IM “searchapp.exe”
rename “c:\windows\systemapps\microsoft.windows.search_cw 5n1h2txyewy\searchapp.bak” “searchapp.exe”
exit

[Difficult_Man]

KIll.bat black window appeared, said selected path could not be found, closed all apps other than Chrome, window disappeared and shortly later Covenant Eyes booted/rebooted.

[Malnutrition]

Now everything is working! (y)

selected path could not be found

That is due to the extra paths, all you need is this below in the kill.bat. If you wish, you can change kill.bat and the shortcut and the shorcut on the start menu.

Meaning open the C:\Users\Bruce Kleinberg\OneDrive\CPM\New Folder\Tools and right click Kill.bat edit and copy and paste this, create new shortcut and move that shortcut to start menu.

Or it’s no big deal really, you can leave it as is, since it works fine that is up to you.
@echo off
“C:\Users\Bruce Kleinberg\OneDrive\CPM\New Folder\Tools\KillEmAll.exe” /auto
“C:\Users\Bruce Kleinberg\OneDrive\CPM\New Folder\Tools\ReduceMemory_x64.exe” /o
exit

---

---

As far as Covenant Eyes: You can stop it from running with this. Create this batch file and rename it CeDeny!.bat

@echo off

:: Kill existing processes
taskkill /F /IM "CEWD.exe"
taskkill /F /IM "CovenantEyes.exe"
taskkill /F /IM "covenanteyescommservice.exe"

:: Block CEWD.exe
icacls "C:\Program Files\CE\CEWD.exe" /inheritance:r
icacls "C:\Program Files\CE\CEWD.exe" /deny "*S-1-1-0:(X)"

:: Block CovenantEyes.exe
icacls "C:\Program Files\CE\CovenantEyes.exe" /inheritance:r
icacls "C:\Program Files\CE\CovenantEyes.exe" /deny "*S-1-1-0:(X)"

:: Block covenanteyescommservice.exe
icacls "c:\program files\ce\covenanteyescommservice.exe" /inheritance:r
icacls "c:\program files\ce\covenanteyescommservice.exe" /deny "*S-1-1-0:(X)"

:: Restart Explorer
taskkill /F /IM "explorer.exe"
start explorer.exe

echo CEWD.exe and CovenantEyes.exe & covenanteyescommservice.exe have been blocked and explorer restarted.
pause

[Difficult_Man]

1. I updated the code in Kill along w/the shortcuts. It closed three different applications instantly w/no error msgs. Covenant Eyes quickly reloaded. CE t is programmed to immediately reload if a user closes the program. Only the Administrator can close the program using the password. I am not inclined to change or get around this.
2. Am I correct in assuming that Kill, in addition to closing applications, also closes non-vital processes working in the background?
3. I suppose now I’ll have to decide which programs go into the Allow list. I’ll have to decide which programs I’ll never want closed in this manner. Like, which programs I’m most likely to be in the middle of using when stalling and freezing occurs.

[Malnutrition]

1– ok, you do you.

2- Yes that is the idea, it’s a kill switch for everything non essential. It was originally part of a game booster that I made and am currently still working on. The idea behind it was to maximize resources for gaming, but I found it could be used for every one especially for machines with low end hardware, such as yours.

3- Ok, but as I stated a few times, you really should not be doing multiple task on this machine, once we are done here you need to start a new thread in the windows 10 sub forum and ask about upgrading your ram modules. 6 gigs would be excellent if your we’re running windows xp; but that’s it.

4-Anything else you want concerning this machine, or are you happy to close as resolved? I imagine it’s running a whole lot better…

[Difficult_Man]

Yes, it is mostly solved. I haven’t used it extensively for a week. I would like to use it on a busy day (like tomorrow) and observe it before closing the thread. I will upgrade RAM asap. I was using multiple programs on this machine before, which is why I assume I can again. But then, I am now using ThinkorSwim and Covenant Eyes, and perhaps Office programs and HTML data are becoming larger?

Re Waking up, I did notice something last week. Originally, waking up was a problem regardless of whether Energy Saver kicked in after being idle, or whether I simply closed the laptop, or whether I used Shutdown>Sleep. We seem to have solved the waking up from Energy Saver/Screensaver and from Shutdown>Sleep. I just discovered that when I simply close the laptop and reopen it later, it still takes forever to become functional. These all seemed like one problem when we started, but apparently there are vastly different ways it hibernates. Any idea why it comes back to life quickly from Sleep and Energy Saver but not from closing?
Thanks again!

[Malnutrition]

It may be hibernating VS sleeping. Click Here
Set it to sleep when you close the lid.

---

---

---

I’d like to see a log from this tool.

[COLOR=rgb(65, 168, 95)]Create and run batch file.

Open a notepad and copy the entire content of the code box below.
[COLOR=rgb(243, 121, 52)]Do not copy the word code!
Paste the txt into the notepad. Save the file to your desktop as [COLOR=rgb(65, 168, 95)]RunPersistance.bat
Now you will right click the on [COLOR=rgb(65, 168, 95)]RunPersistance.bat and run as administrator.

@echo off
powershell -Command "Set-ExecutionPolicy Unrestricted  -Force"
powershell -Command "Install-Module PersistenceSniper -Force -ErrorAction Stop"
powershell -Command "Import-Module PersistenceSniper -ErrorAction Stop"
powershell -Command "Find-AllPersistence | Out-File "%UserProfile%\OneDrive\Desktop\Persistence_Sniper_Result.txt"
notepad "%UserProfile%\OneDrive\Desktop\Persistence_Sniper_Result.txt"
exit

---

---

It will scan your machine for unusual start up areas.
A log will be create on the desktop when it is done.
Named [COLOR=rgb(65, 168, 95)]Persistence_Sniper_Result
Attach that in your next reply.[/COLOR][/COLOR][/COLOR][/COLOR][/COLOR]

[Malnutrition]

@Difficult_Man How are things now?

[Difficult_Man]

Much better. I have used it for two days, with slightly different results. Mixed results using KillEmAll. Overall, much better. Still need to complete the last worklist, which I hope will also help.

[Difficult_Man]

The first time I used Kill was very difficult. I believe Window was automatically updating because the computer was dreadfully slow and I got a notification that I needed to shutdown and restart. It took forever just to open Start and click KIll. Second time I used Kill things were just generally slow. I don’t remember if it got better.

Excel seems to be the slowest to switch to when it has been idle. It has the most hiccups. Once I’ve used it for five minutes, it functions well. Many things are copied to the system just in case there’s a crash. After Excel, I would say Chrome (again, after being idle for a few minutes).

[Malnutrition]

So you are telling me that stopping all non windows processes and services slows your computer.

Post the log when you get a chance please.

[Difficult_Man]

OK. I may be able to do those things late tonight.

Kill doesn’t slow the computer. There were either one or two times when it didn’t make a noticeable difference. That may have been while Windows Automatic Updates was doing its thing. I haven’t needed to use it today or yesterday.

[Malnutrition]

If you are having issues running the previous instructions, we will do it thru FRST.

FRST Fix.

Download attached fixlist.txt file and save it to the Desktop.
NOTE. It’s important that both files, FRST/FRST64 and fixlist.txt are in the same location or the fix will not work.
Right Click Run FRST64 as admin; and press the Fix button just once and wait.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
After that let the tool complete its run.
When finished FRST will generate a log on the Desktop (Fixlog.txt).
Please post it to your reply.

This will create a new.txt file named [COLOR=rgb(243, 121, 52)]Persistence_Sniper_Result.txt attach it for me please.[/COLOR]

[Difficult_Man]

I created and ran the .bat file and got this in the black window:
NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘2.8.5.201’ or newer to interact with NuGet-based repositories. The NuGet
provider must be available in ‘C:\Program Files\PackageManagement\ProviderAssemblies’ or ‘C:\Users\Bruce
Kleinberg\AppData\Local\PackageManagement\Provider Assemblies’. You can also install the NuGet provider by running
‘Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force’. Do you want PowerShellGet to install and import
the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is “Y”):

I thought I’d check w/you before saying Yes…[/S]

[Malnutrition]

Yes install it.