New
#31
Right click the recycle bin on your Desktop and select Properties and select the partition where you want to disable recycle bin and select “Don’t move files to the Recycle Bin.” Click Apply and OK buttons.
Recycle Bin in recovery partition filling
-
-
New #32
I decided to give Mini PW a try and for this purpose it WAS useful!
There is still a Recycle bin. Maybe I should have deleted it before changing partition id? I did a test by deleting some more desktop short cuts. They show in main recycle bin, but not here. So, hopefully this issue is SOLVED ??
I still have a problem with laptop. This afternoon, just restarted it. It again says "Getting Windows Ready" Don't turn off your computer. Last night it did same and after 2-3 hours, I went to bed. In morning it was off, but started up OK. Is this Win10 still updating or what? Anyway to determine just what it is doing or at what stage updates are.
-
New #33
Run this log collector and post a zip into the thread for troubleshooting:
log collector v2-beta06.zip
-
New #34
If you had tried to do that from within Windows it would have just recreated $RECYCLE.BIN again - same goes for the 'System Volume Information' folder. You'd have to boot from another OS like a Linux Live USB to be able to delete them.
Anyway, they are not the cause of your other problems. They play no part in the recovery environment and will just be ignored. I have them on my recovery partition (a relic of a time I changed its ID and gave it a drive letter to let me explore it) and my system is fully functional. Just ignore them - they do no harm by being there.
-
New #35
The recycle bin in recovery may be able to be deleted using diskpart.
If you want to do this then you will need to backup all files and make a backup image using Macrium.
-
New #36
I am not going to worry about it. This old Toshiba is not going to be around for too long. We will probably pick up a new laptop with Win 10 installed and then just transfer my wife's stuff over to it. Whille it still works, I will use the Toshiba to learn something about Win 10. But for every day use I am sticking with my Lenovo Thinkpad with Win 7 Pro.
By the way, the Toshiba did restart after a couple of hours. I guess I should check and see where it is with updates. Or Fix Updates?
-
New #37
Use WinKey+R, run Winver and see what it says. Latest version is 1709, os build 16299.192
Open Settings > Update & Security, pending updates (if any) will be listed here.
Click 'View installed update history' to see successfully installed (or not) updates.
BTW, which model is this 'old Toshiba'? I only ask because I've been happily using Windows 10 on an 'old Toshiba' for years :)
-
New #38
It is ver 1709, build 16299.125.
Says "There were some problems installing updates. If you keep seeing this etc etc search on-line for 0x800705b4."
Tried one "solution" and it required a restart. Guess what, back in another endless loop.
It is a Toshiba Satellite - Model L300, I think. Not a keeper for my wife, mainly because I had to "fix" GPU to mother board connection with a propane torch (twice!) I will use it as a test bed!
Glad to hear that the Win10 free updates are tied to the computer. I had Win 10 fail on my Lenovo Thinkpad T520. Luckily, I had the Key for the original Win 7 installation, so I installed Win7. Much happier, but from what was said, I could also install Win 10, if I wished. I do have a spare 256G SSD.
-
-
New #39
That's the version from December's 'Patch Tuesday' cumulative update, so reasonably up to date. There was one out of band cumulative update since then, Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192, but a number of people have reported problems installing that one - it's not something specific to your 'old Toshiba'.
-
New #40
Any suggestions welcomed! On every restart, just get that "Getting Windows Ready" Don't turn off your computer. blue screen. Makes computer unusable. I have read a lot of "fixes" on net for the 0x800705b4 issue, but that same number seems to cover many issues some of which have been around for years.
Do you think it just that latest update that is causing the problem?
Quote
Related Discussions
