Main Area and Open Discussion > Living Room
Win10 Navigation Pane scrambled
Stoic Joker:
Chances are you have one of the many organize/view settings set to sort the drives by free/used space, or drive size. Which is usually easy to spot in a screen shot.
Personally I have a standing request for all clients to send a SS of any and all error messages they get for an issue, as frequently the type of window will tell you more about an issue than the poorly worded error message. Not to mention that users never read the entire message, or pay attention to the caption bar text.
So Yeah...a picture really does paint - or save the exchange of - 1,000 words.
-Stoic Joker (October 03, 2014, 10:49 PM)
--- End quote ---
Thanks for the reply, Stoic Joker, and I agree that users often never read the entire msg but I'm afraid I've never found screenshots to be of much value when troubleshooting. And of course, to get a screenshot off a flawed O/S install is another challenge.
I might also refer you to my reply #5 on this thread, both above and below at this point and ask you that same question I asked Tomas.. screenshots and corrupt files? Not just on a different page but in a completely different book!
And I'm still looking for the option to sort the Navigation Pane. There are sort options all over the page but the one for the Nave Pane eludes me :huh:-Cuffy (October 04, 2014, 12:53 PM)
--- End quote ---
If the shell loads, the shell loads...so the relevance of corrupt files dims considerably. Just because it's a TP doesn't alter the fact that it's a beta OS e.g. Hell it could have been delivered that way.. ;) So, once the shell has loaded it is entirely up to the user to decide how what is going to be configured and displayed. so if by chance you got lucky with an accidental UI hotkey that borked the displayed drive order ... Hay IT happens.
I actually just went through an issue exactly like this a few weeks ago with a client that - even though they had a CS degree - thought that another vendor had torched their file system because none of the folders they had in their documents were there and files from another location were showing up merged and comingled with their "local" stuff.
They spent two day trying to sort this out, and then called me. had they sent an SS I could have told them on the phone what to do...but they just kept insisting on it being a major problem that restoring from backup hadn't fixed. However when I got onsite, it only took seconds to resolve the issue...But those seconds cost them $100...because I had to go onsite. You see their only issue was that the Arrange By option was set to name, instead of Folder ...(easily visible in an SS)... Which caused the shell to omit the existence of folders from the current view and just show the files (at the default library level) in one big disorganized lump.
So the shell was doing exactly what it was told to do ... It just wasn't what the user wanted.
The snipping tool has been built into Windows for a really long time now...so getting a screen shot isn't in the least bit hard. Hell I've had field techs send me pics of POST errors from their phones in the interest of getting something resolved (and it worked).
Not to mention that like many of us here on the board...Talking to me in person (professionally...) is really expensive ... So when free help is offered -- Damn it man go with the flow... :D
Cuffy:
And I'm still looking for the option to sort the Navigation Pane. There are sort options all over the page but the one for the Nave Pane eludes me huh
--- End quote ---
Thanks for the reply but if there was help there I missed it.
I thought it was only fair to give you an update of what is transpiring here.............
I downloaded the 32 bit ISO for the Win10 Preview.
Burned it to a DVD using Image Burn.
Clean install on a 64 bit machine.
Install finishes, a bright multicolored rainbow background appears.
Hit the space bar and the login appears.
I log in and open File Explorer.
The drive letters in Navigation Pane are not in alphabetical order. Strange but it is a beta, and I usually run them if I have a slot to put them in. Having read that users were having problems with installing I did a little checking and then posted to DC hoping the problem I was having was the same as the one others were having.
Having run many betas previously I started System File Checker and it found corrupt files, some of them it couldn't fix.
It also produced a log of errors it found that ran 3700kb and one helluva long scroll to read.
Completely unacceptable and I think it was about that time I posted what I had found to DC.
Having nothing to lose I ran setup again in an "over the top" install.
When that finished the Nave Pane was still in the same non-alphabetical order so I punched up SFC, again from an elevated command prompt, and when finished that reported "un-fixable" files, Nave Pane no improvement, but the log file of errors had dropped to 2100kb. Some improvement but still unacceptable!
I began getting advice from DC and a request for a screenshot. Apparently I had set something wrong and the Nave Pane wound up out of alphabetical order.
Since I have a virgin, default install in front of me and I haven't "set" anything, combined with the knowledge that the Navigation Pane is not, I repeat... Not, sortable by a user, I chose to disregard all that free advice and ask some questions.
The next step is to give Windows "Repair"/Reset a go.
Inserted the DVD and rebooted.
The install screen opened and I selected "Repair".
I immediately got a response "Your computer is not repairable".
Having some experience in the field, I immediately suspected a bad burn and proceeded to burn another DVD from my original downloaded ISO.
Got a mess on Drive C: on that machine so a clean install is essential.
A clean install with a freshly burned DVD duplicated the original install.
Simple deduction tells me "hey buddy, you got a bad download! Seems reasonable to me under the circumstances.
The machine with the bad install sat there awhile, HDD light flickered occasionally, and then the light flickered rapidly and the machine emitted a strange sound repeatedly until I hit the reset button and got it shut down.
With a five and a half hour download required to get fresh install media I think I'll wait awhile.
A new release by MS might give me a better shot at a compatible ISO.
That about brings things up to the minute! Is there anything here that you can agree with?
:)
Shades:
As far as I know, each partition on a hard disk is assigned a volume serial code by the NTFS file system first, then a drive-letter is assigned. Possibly the sort order in the pane sorts on volume serial instead of the drive letter as you expect.
This is quite low-level and most likely to be altered in the registry. Fixing this could take as much as downloading a new fresh iso...which is most likely the better option as you don't trust the copy you have at hand. At least there is also a 64-bit iso to play with. :)
Cuffy:
You are right about the serial numbers and I spent an hour crawling the registry trying to find a place to change the sort order, all to no avail. Considering everything else that's turned up I'm going to check out some other ideas before I download another ISO.
That machine ran Win7/32 Pro since it was released but it has a Celeron D CPU so it will run a 64 bit O/S.
I didn't download a 64 bit ISO because I'd seen reports where people were having problems with it. I have no intention of upgrading to Win10 so I thought I'd give the 32 bit version a shot to see what the hype was all about. If I have to re-download I'll get the 64 bit ISO.
In the meantime I'm going to check that machine out a little more thoroughly. I've got a cigar box full of memory sticks and just before I stopped using the machine fulltime I was looking for some memory for my nephew. I found a couple of 500mb sticks that would fit that machine and since it had the slots and only 2gb memory I dropped in the two 500mb chips.
I didn't use the machine much after that but it reported the memory, ran fine, and gave it a little performance boost.
Since the Win10 install went belly up and especially after the strange noises after the machine sat there awhile, that old memory has become suspect. I think my next move will be to pull that memory and then re-install from the last DVD I burned. I don't remember if Win10 requires more than 2gb mem to run or not but I'll get some idea if the memory is corrupting the install or if the media is already corrupt.
Sorry for the ramble...............
:)
wraith808:
As far as I know, each partition on a hard disk is assigned a volume serial code by the NTFS file system first, then a drive-letter is assigned. Possibly the sort order in the pane sorts on volume serial instead of the drive letter as you expect.
This is quite low-level and most likely to be altered in the registry. Fixing this could take as much as downloading a new fresh iso...which is most likely the better option as you don't trust the copy you have at hand. At least there is also a 64-bit iso to play with. :)
-Shades (October 04, 2014, 05:20 PM)
--- End quote ---
That's the other option that I've seen- in the disk management utility, you can change that sort order. Because I had an old drive with windows, and then installed another drive and set that to C, that drive was in the wrong order. I was able to fix it in the disk management utility.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version