In Progress Forever to Wake Up

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
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...
 
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!
 
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.


Create and run batch file.


Open a notepad and copy the entire content of the code box below.
Do not copy the word code!
Paste the txt into the notepad. Save the file to your desktop as RunPersistance.bat
Now you will right click the on RunPersistance.bat and run as administrator.

Code: 
@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 Persistence_Sniper_Result
Attach that in your next reply.
 

Attachments

Last edited:
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.
 
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).
 
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.
 
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.
 
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 Persistence_Sniper_Result.txt attach it for me please.
 

Attachments

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\ProviderAssemblies'. 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 Suspend [?] Help (default is "Y"):

I thought I'd check w/you before saying Yes...
 
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\ProviderAssemblies'. 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?

I thought I'd check before responding...


Also, I used Kill this morning when I had trouble closing Zoom. When I reopened Zoom the microphone and camera were turned of and inaccessible. It gave me a link to the settings but the actionable buttons were greyed out. I restarted the computer and Zoom and the microphone and camera are still turned off.

As far as the Kill logs, I've run it maybe four times. I assumed it over-writes the log each time, but what I saw dates from a week ago. I hope it's helpful.
 

Attachments

  • Screenshot (749).webp
    Screenshot (749).webp
    35.3 KB Views: 5
  • Screenshot (748).webp
    Screenshot (748).webp
    47.3 KB Views: 3
  • Screenshot (747).webp
    Screenshot (747).webp
    55.2 KB Views: 5
Tried to run Persistance.bat. Here's what I got in red:

Out-File : Cannot validate argument on parameter 'Encoding'. The argument
"Kleinberg\OneDrive\Desktop\Persistence_Sniper_Result.txt" does not belong to the set
"unknown,string,unicode,bigendianunicode,utf8,utf7,utf32,ascii,default,oem" specified by the ValidateSet attribute.
Supply an argument that is in the set and then try the command again.
At line:1 char:47
+ ... \Users\Bruce Kleinberg\OneDrive\Desktop\Persistence_Sniper_Result.txt
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Out-File], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.OutFileCommand
 
Kill em is only temp it does not make any permanent changes what so ever, it only closes processes.
So using KillemAll to close processes is the same as you clicking to close, you just do not have to do it manually.
So whatever is going on with Zoom is it's own issue. Remove with GeekUninstaller and reinstall it.
Kill em all will also not create a log with the batch file you would have to run it directly.
Here is the new Run Persistance that will deal with encoding issues.
 

Attachments

As far as the microphone and such being disabled.

Code: 
@echo off
powershell -Command "Get-AppXPackage -Name *Microsoft.Windows.Photos* | Reset-AppXPackage"
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone" /v "Value" /t REG_SZ /d "Allow" /f
reg add "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone" /v "Value" /t REG_SZ /d "Allow" /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\webcam" /v "Value" /t REG_SZ /d "Allow" /f
reg add "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\webcam" /v "Value" /t REG_SZ /d "Allow" /f
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Privacy" /v "LetAppsAccessMicrophone" /t REG_DWORD /d 1 /f
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Privacy" /v "LetAppsAccessCamera" /t REG_DWORD /d 1 /f
pause
 
Ran FRST scan. A Notepad file of Scan Log or Resutls opened up. Because it was blank I closed it. Then the Fix log opened up and it was populated. I thought I might have closed the log prematurely, before it populated so I ran the scan again (after the fix). So, here is that log, for what it's worth.

Ran Persistance but not much seems to have happened. The Persistance Sniper Result is an empty file.

Will uninstall/reinstall Zoom while I'm waiting for your response.
 

Attachments

You must log in or register to reply here.
Top Bottom