If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Win-10 weirdness again update- even weirder
I wrote recently that the start menu was working again. Well, after
the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. Looking at my log, I saw that the only thing I had changed since it was working was to turn "use my sign in info..." in sign-in options to OFF. Note that the start menu was working at that time, with the setting ON. So when I found start menu not working, I brought up the settings app via ms-settings: in firefox so I could try turning that setting back on. There I discovered that the setting was already reset to ON, So I set it OFF again.. Then the start menu worked normally again. Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? BTW, the two programs with which I struggled to get to autostart have continued autostarting just fine once they, for no known reason, began to do so a few days ago. Screen saver still might work once every few days. Here's a function that has worked perfectly in Windows versions going back at least to XP, yet malfunctions in this wonderful new ultra-stable Windows-10. (OK, satire off.) -dan z- -- Someone who thinks logically provides a nice contrast to the real world. (Anonymous) |
Ads |
#17
|
|||
|
|||
Win-10 weirdness again update- even weirder
On 9/22/2018 9:45 AM, slate_leeper wrote:
I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. What icons were there? Did it include the Settings icon? Looking at my log, I saw that the only thing I had changed since it was working was to turn "use my sign in info..." in sign-in options to OFF. Note that the start menu was working at that time, with the setting ON. So when I found start menu not working, I brought up the settings app via ms-settings: in firefox so I could try turning that setting back on. There I discovered that the setting was already reset to ON, So I set it OFF again.. Why did you use FireFox instead of the Settings icon? Then the start menu worked normally again. Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? Have you tried the "Learn More" link to understand what that option is actually doing? BTW, the two programs with which I struggled to get to autostart have continued autostarting just fine once they, for no known reason, began to do so a few days ago. Screen saver still might work once every few days. Here's a function that has worked perfectly in Windows versions going back at least to XP, yet malfunctions in this wonderful new ultra-stable Windows-10. (OK, satire off.) Win10 is as different from XP as using an OS from another company, so if this is your first OS after XP I'd recommend tossing almost all of the practices involved in using that OS in order to maintain some semblance of sanity. ;-) -- best regards, Neil |
#18
|
|||
|
|||
Win-10 weirdness again update- even weirder
slate_leeper wrote:
I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. Looking at my log, I saw that the only thing I had changed since it was working was to turn "use my sign in info..." in sign-in options to OFF. Note that the start menu was working at that time, with the setting ON. So when I found start menu not working, I brought up the settings app via ms-settings: in firefox so I could try turning that setting back on. There I discovered that the setting was already reset to ON, So I set it OFF again.. Then the start menu worked normally again. Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? BTW, the two programs with which I struggled to get to autostart have continued autostarting just fine once they, for no known reason, began to do so a few days ago. Screen saver still might work once every few days. Here's a function that has worked perfectly in Windows versions going back at least to XP, yet malfunctions in this wonderful new ultra-stable Windows-10. (OK, satire off.) -dan z- So it's something related to this page ? https://www.tenforums.com/tutorials/...dows-10-a.html If the OS is restoring previous applications, the *Start menu is an App*. Cortana is an App. MSEdge is an App. Maybe the OS uses the "in-box" bit in the App database, to figure out things it should not be restoring. (Things that come up on their own at startup.) Paul |
#19
|
|||
|
|||
Win-10 weirdness again update- even weirder
On Sat, 22 Sep 2018 11:06:27 -0400, Neil
wrote: On 9/22/2018 9:45 AM, slate_leeper wrote: I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. What icons were there? Did it include the Settings icon? Yes, put clicking it produced only the white box, not the app. Looking at my log, I saw that the only thing I had changed since it was working was to turn "use my sign in info..." in sign-in options to OFF. Note that the start menu was working at that time, with the setting ON. So when I found start menu not working, I brought up the settings app via ms-settings: in firefox so I could try turning that setting back on. There I discovered that the setting was already reset to ON, So I set it OFF again.. Why did you use FireFox instead of the Settings icon? As above, couldn't use the settings icon. Then the start menu worked normally again. Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? Have you tried the "Learn More" link to understand what that option is actually doing? It says it allows my account to "automatically sign in" so updates can be completed. 1) My account already automatically signs in, as I have no password. 2) There were no updates between the working/not working/working again events. BTW, the two programs with which I struggled to get to autostart have continued autostarting just fine once they, for no known reason, began to do so a few days ago. Screen saver still might work once every few days. Here's a function that has worked perfectly in Windows versions going back at least to XP, yet malfunctions in this wonderful new ultra-stable Windows-10. (OK, satire off.) Win10 is as different from XP as using an OS from another company, so if this is your first OS after XP I'd recommend tossing almost all of the practices involved in using that OS in order to maintain some semblance of sanity. ;-) Actually, I STILL use XP under VirtualBox. I have some accounting programs written by me decades ago that run in 16 bit only. Also an old addictive game that works and looks much better with the old version under XP than the "updated" version for Win-10 does. BTW, the XP screen saver still works under VirtualBox. -dan z- -- Someone who thinks logically provides a nice contrast to the real world. (Anonymous) |
#20
|
|||
|
|||
Win-10 weirdness again update- even weirder
On Sat, 22 Sep 2018 11:47:48 -0400, Paul
wrote: slate_leeper wrote: I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. Looking at my log, I saw that the only thing I had changed since it was working was to turn "use my sign in info..." in sign-in options to OFF. Note that the start menu was working at that time, with the setting ON. So when I found start menu not working, I brought up the settings app via ms-settings: in firefox so I could try turning that setting back on. There I discovered that the setting was already reset to ON, So I set it OFF again.. Then the start menu worked normally again. Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? BTW, the two programs with which I struggled to get to autostart have continued autostarting just fine once they, for no known reason, began to do so a few days ago. Screen saver still might work once every few days. Here's a function that has worked perfectly in Windows versions going back at least to XP, yet malfunctions in this wonderful new ultra-stable Windows-10. (OK, satire off.) -dan z- So it's something related to this page ? https://www.tenforums.com/tutorials/...dows-10-a.html If the OS is restoring previous applications, the *Start menu is an App*. Cortana is an App. MSEdge is an App. Maybe the OS uses the "in-box" bit in the App database, to figure out things it should not be restoring. (Things that come up on their own at startup.) Paul Will, what that page describes and how it can be reset certainly sounds exactly like what is happening to me. I still believe in the term "weird." grin Thank you. Now I won't worry about it so much, since resetting it is reasonably simple. This page allowed me to do that by running the settings app when the settings icon was non-functional: https://www.thewindowsclub.com/creat...-in-windows-10 The page says they are URLs, so I entered ms-settings:signinoptions into Firefox, which gave a prompt re acceptance, and then brought up the app. Cool. -dan z- -dan z- -- Someone who thinks logically provides a nice contrast to the real world. (Anonymous) |
#21
|
|||
|
|||
Win-10 weirdness again update- even weirder
On Sat, 22 Sep 2018 17:27:06 +0100, ? Good Guy ?
wrote: On 22/09/2018 14:45, slate_leeper wrote: I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. I think you'll need to start producing images or short videos so that we can follow what exactly is happening. I have never seen a Windows 10 machine giving so much trouble to anybody. In your case you have a brand new machine with very powerful processor so it is even more puzzling to me. It looks like you may need to return the machine to the retailer or if you can't do that, you may need to buy a new machine from DELL or HP so that it has a warranty of 1 year (default) and you can extend it to 3 or 4 years by paying a small fee. I Already have the extended premium warranty. Dell was able to solve the problem back when the 1803 update would not install even from the ISO disk. (see previous posts). I have to conclude that the the problem is with the hardware so start with the hard disk as it is not recording and/or retaining the data. There are about 950 million users of windows 10 and very few of them have ever complained like you have. Are you in the habit of downloading pirated stuff like software and pdf books? If the answer is yes or sometimes then it might be the main source of problems. There are two pirates frequenting these newsgroups who are posting links to these dodgy sites so be careful what you do with them. No on the downloading. Yes on the tinkering. That is why I now keep logs, so I can "untinker" if necessary. Always been a go-faster guy. I used to spend thousands to make a race car a tenth-of-a-second faster. Now I spend hours trying to bend a computer to doing things my way, a tenth-of-a-second faster. I am also a "privacy nut." Just the way I am. Sorry. On the other hand, nothing I have had problems with is unique. Google searches show many are having the same problems. And nothing I have done SHOULD have caused problems, since I am simply adjusting settings provided in Windows-10. -dan z- -- Someone who thinks logically provides a nice contrast to the real world. (Anonymous) |
#22
|
|||
|
|||
Win-10 weirdness again update- even weirder
On 9/23/2018 8:38 AM, slate_leeper wrote:
On Sat, 22 Sep 2018 11:06:27 -0400, Neil wrote: On 9/22/2018 9:45 AM, slate_leeper wrote: I wrote recently that the start menu was working again. Well, after the next system reboot, it went back to icons only. Anything typed produced a white box, with the typed letters otherwise ignored. What icons were there? Did it include the Settings icon? Yes, put clicking it produced only the white box, not the app. Perhaps there is some process blocking completion of opening of the Start Menu programs. Have you looked at Task Manager while the white box is visible to check the running processes and how many system resources they're consuming? Why would that setting have anything to do with the start menu, especially turning it OFF when the start menu worked previously with it ON? Have you tried the "Learn More" link to understand what that option is actually doing? It says it allows my account to "automatically sign in" so updates can be completed. 1) My account already automatically signs in, as I have no password. 2) There were no updates between the working/not working/working again events. That implies that the problem has nothing to do with either the auto sign in or updates. I would suspect some app or process as the cause. Task manager and Error Logs may offer the most helpful insights. -- best regards, Neil |
#23
|
|||
|
|||
Win-10 weirdness again
On Mon, 17 Sep 2018 20:28:03 -0500, VanguardLH wrote:
slate_leeper wrote: Win-10-64bit-Pro Weird 1: After rebooting the computer, pressing the Windows key results only in a blank white box. Anything typed is ignored. 1 to 2 hours later, it starts showing the normal dark gray box and the icons I have selected. However anything typed is still ignored. Clicking the "All Apps" icon gives the list. Clicking on Cortana gives the search box. Typing anything results in the blank white box. Same result when pressing WindowsKey+S. Task Manager shows Cortana as "suspended." There seems to be no option to un-suspend.sfc /scannow found and fixed one corrupted file, OneDrive.lnk. I don't use OneDrive, and can't imagine this being the problem. The DISM checkhealth option reported "no component store corruption detected." One website suggested shellexperiencehost being suspended might be causing the problem, and that would show in TaskManager. TaskManager does show Windows Shell Experience host as suspended, but again I found no information on how to un-suspend. Since you haven't looke at the Event Viewer to check, and to start checking anew, I'd clear the events in Event Viewer and reboot. Then look at Event Viewer to see what non-informational messages it had. Advising someone who may not know better to clear their Event logs is supremely bad advice. Instead, just use the filters that are provided. It's easy to look at any desired time period using the available filters. When you clear the logs, everything logged is gone for good, which is definitely not something anyone should suggest to others. Clear your own logs if you like, but not someone else's. IMHO, of course. |
#24
|
|||
|
|||
Win-10 weirdness again
On Wed, 19 Sep 2018 22:18:52 +1200, Eric Stevens
wrote: On Tue, 18 Sep 2018 04:55:34 +0100, ? Good Guy ? wrote: If you are using SSD then forget it. You won't be able run Windows 10 on it because 256GB is not enough with all that software and regular updates. I know people don't agree with this but I am speaking from experience. My machine came with 256GBSSD and 2TB normal WD hard disk. I foolishly installed Windows 10 Professional on SSD and the problem started (for nearly 1 month). I then switched everything to 2TB HD and the problem went away and I am very happy with the machine. SSD is a complete waste of money (& time) IMO. I'm running Windows 10 quite happily on 512 GB of SSD and 2 TB of HD. Also 32 GB of RAM. And I'm running Adobe CC, PS and LR, quite happily. In case you weren't aware, "Good Guy" is one of our local village idiots here in the Windows 10 group. Whatever his advice is, the opposite will generally serve well. |
#25
|
|||
|
|||
Win-10 weirdness again
Char Jackson wrote:
On Mon, 17 Sep 2018 20:28:03 -0500, VanguardLH wrote: slate_leeper wrote: Win-10-64bit-Pro Weird 1: After rebooting the computer, pressing the Windows key results only in a blank white box. Anything typed is ignored. 1 to 2 hours later, it starts showing the normal dark gray box and the icons I have selected. However anything typed is still ignored. Clicking the "All Apps" icon gives the list. Clicking on Cortana gives the search box. Typing anything results in the blank white box. Same result when pressing WindowsKey+S. Task Manager shows Cortana as "suspended." There seems to be no option to un-suspend.sfc /scannow found and fixed one corrupted file, OneDrive.lnk. I don't use OneDrive, and can't imagine this being the problem. The DISM checkhealth option reported "no component store corruption detected." One website suggested shellexperiencehost being suspended might be causing the problem, and that would show in TaskManager. TaskManager does show Windows Shell Experience host as suspended, but again I found no information on how to un-suspend. Since you haven't looke at the Event Viewer to check, and to start checking anew, I'd clear the events in Event Viewer and reboot. Then look at Event Viewer to see what non-informational messages it had. Advising someone who may not know better to clear their Event logs is supremely bad advice. Instead, just use the filters that are provided. It's easy to look at any desired time period using the available filters. When you clear the logs, everything logged is gone for good, which is definitely not something anyone should suggest to others. Clear your own logs if you like, but not someone else's. IMHO, of course. It all rolls out, anyway (expires). If users haven't been monitoring their logs, the old records disappear. Expiration is not by date but by volume of new records. Looking at logs only has value to see the rate of repetition for a particular event. History has value only if you actually want the history. Look at the OP's posts. You really think the OP gives a gnat's fart about old records? He want to find out what happened NOW. Saying that the OP must keep the old logs that he won't be reviewing is a nebulous suggestion. Maybe YOU want to see if the same event got recorded 2 weeks or 2 months ago but that doesn't appear to be what the OP wants to do. Per your own advice, the OP should filter out all the old logs, so he won't see them. Well, that's my suggestion does, too. However, with huge-sized logs just to keep around records you don't care about and won't be using because, gee, you'll be filtering them out, makes using the viewer can be laggy. A lot faster to scroll through a few thousand log entries than 20 million. |
#26
|
|||
|
|||
Win-10 weirdness again
On Mon, 24 Sep 2018 20:47:08 -0500, VanguardLH wrote:
Char Jackson wrote: On Mon, 17 Sep 2018 20:28:03 -0500, VanguardLH wrote: slate_leeper wrote: Win-10-64bit-Pro Weird 1: After rebooting the computer, pressing the Windows key results only in a blank white box. Anything typed is ignored. 1 to 2 hours later, it starts showing the normal dark gray box and the icons I have selected. However anything typed is still ignored. Clicking the "All Apps" icon gives the list. Clicking on Cortana gives the search box. Typing anything results in the blank white box. Same result when pressing WindowsKey+S. Task Manager shows Cortana as "suspended." There seems to be no option to un-suspend.sfc /scannow found and fixed one corrupted file, OneDrive.lnk. I don't use OneDrive, and can't imagine this being the problem. The DISM checkhealth option reported "no component store corruption detected." One website suggested shellexperiencehost being suspended might be causing the problem, and that would show in TaskManager. TaskManager does show Windows Shell Experience host as suspended, but again I found no information on how to un-suspend. Since you haven't looke at the Event Viewer to check, and to start checking anew, I'd clear the events in Event Viewer and reboot. Then look at Event Viewer to see what non-informational messages it had. Advising someone who may not know better to clear their Event logs is supremely bad advice. Instead, just use the filters that are provided. It's easy to look at any desired time period using the available filters. When you clear the logs, everything logged is gone for good, which is definitely not something anyone should suggest to others. Clear your own logs if you like, but not someone else's. IMHO, of course. It all rolls out, anyway (expires). If users haven't been monitoring their logs, the old records disappear. Expiration is not by date but by volume of new records. "It all rolls out anyway" tells me that you simply don't get it. Event logs are only useful if they exist. Deleting everything makes them useless. Deleting everything so you can see what's new is just dumb because you can use the provided filters to see the new stuff. Like I said, clear your own logs anytime you like, but it's irresponsible to suggest someone else should do it. Besides the OP, others read posts here and might accidentally take your bad advice. Looking at logs only has value to see the rate of repetition for a particular event. Not true, and you know it. Single events can be just as valuable as repeated events. History has value only if you actually want the history. Look at the OP's posts. You really think the OP gives a gnat's fart about old records? He want to find out what happened NOW. You have no clue what the OP wants, nor do you have a clue what anyone else who might come along and see your bad advice wants. Today, the OP looks like he's trying to address a specific issue, but tomorrow he might want to work on another issue and the advice might be to check his event logs. His reply? "You mean the logs you told me to delete yesterday?" Saying that the OP must keep the old logs that he won't be reviewing is a nebulous suggestion. Maybe YOU want to see if the same event got recorded 2 weeks or 2 months ago but that doesn't appear to be what the OP wants to do. Per your own advice, the OP should filter out all the old logs, so he won't see them. Well, that's my suggestion does, too. Unless I completely misread your post, your suggestion was to DELETE the event logs ("clear the events in Event Viewer and reboot". Filtering and deleting are not even close to being the same thing. You know better. However, with huge-sized logs just to keep around records you don't care about and won't be using because, gee, you'll be filtering them out, makes using the viewer can be laggy. A lot faster to scroll through a few thousand log entries than 20 million. That's absolutely untrue, but you wouldn't know it because...wait for it...you've probably screwed up your own event logs, too. If you can get access to a system that you haven't screwed up, go ahead and give it a shot. Use the filters to view a single day's worth of events, or whatever period suits your fancy. Notice any lag? No, of course not. |
#27
|
|||
|
|||
Win-10 weirdness again
Char Jackson wrote:
You have no clue what the OP wants, Careful. Your logic applies to YOU, too. |
#28
|
|||
|
|||
Win-10 weirdness again
On Tue, 25 Sep 2018 12:33:39 -0500, VanguardLH wrote:
Char Jackson wrote: You have no clue what the OP wants, Careful. Your logic applies to YOU, too. Exactly, but preserving information is always safer than destroying it, especially when it belongs to someone else. Thanks for helping me make my point. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|