Just a few more items to add to the list
Just the other day I was copying and pasting some files from my hard-drive to my network storage device using Windows Explorer. Needless to say the copy process took 5 attempts to copy the selected files to the remote device as each time I attempted to copy the files from the source to the destination I was prompted by a different error.
For example:
1) Unable to copy file test.txt because access is denied. This occurred because the NTFS file system lost the ownership information on the file and the NTFS permissions were no longer retained in the file security section of the file. Of course the first thing I attempted was to push the parent file system permissions down to the child objects. Of course this did as I told it to do however the file with the missing Ownership information again neglected to inherit the file system permissions. So after manually taking ownership of the file then pushing out the file permissions over again was I able to copy the file successfully.
2) Following this error I was unable to copy another file because somehow the file name was too long for the copy process to copy. Once again halting my copy process and having me to start all over from the beginning. I'm not sure how it let me create a file that was too long in length in the first place? What's the point of creating a file you can't do anything with?
Anyway, each time the copy process failed I had to restart the copy process from the beginning as I wasn't sure what was copied and what wasn’t. So to ensure all files transferred properly I started the copy process over from the beginning. Finally I had success! All my files were transferred from the hard-drive to Network Storage Device.
Now my suggestion and question would be: Wouldn't it make more sense to not halt on a file copy error but continue on to the next file and after the file copy process finishes generate a report indicating the files & their extensions with their associated folder path that failed to copy instead of stopping the copy and paste process and having to start all over again?
In my opinion that would make me a more efficient user.
3) Also, I have found that moving large amounts of data from one folder to another on the same volume or from one logical partition to another takes longer in windows 7 than it did in XP. Would that be because of the system overhead or is the embedded Windows Defender service scanning each file as it copies?
4) The "Run as administrator" context menu doesn't always show up when right clicking on a program. Instead, the hidden method of CTRL + Shift needs to be pressed before selecting the program to run. Just a little frustrating bug I've noticed.
5) Windows 7 does not indicate which folders are shared network folders when browsing files in windows explorer. More of an inconvenience than a bug. I miss that little helping hand it made me more efficient.
6) When attempting to start an existing VPN connection from the network icon in the notifications center in Windows 7. The connection displays the error: This connection requires an active internet connection when attempting to click the connect button. Even though the PC has internet access. VPN connections are unable to be established. A work around to this Windows 7 glitch is to navigate to the Control Panel> Network and Internet > Network Connections and manually select the VPN connection to start it from there. Frustrating, but thank goodness there’s more than one way to skin a cat in Windows 7 =)
7) Wouldn't it be nice to be able to Slipstream a Windows 7 service pack into a Windows 7 image without having to do a clean install of the operating system just to integrate a service pack? This would make me definitely a more efficient user. I miss the old ServicePack.exe /integrate:C:\i386
8) User's cannot create a Documents System Icon on their Desktop like in XP. So much for efficiency. Now a junction point has to be used to create a folder Similar to the My Documents Folder in XP using a traditional DOS prompt window. Seems like a step backwards not forward thinking. Here would be the syntax: mklink /D "My Documents" C:\Users\MyProfileName\Documents
It would be nice if these fixes were included in a Service Pack release instead of just using service packs as an accumulation of known security updates. I better stop here for now before this article gets too long & boring.
I guess stating the obvious truth doesn't get a person very far.
I'm not full of crap, but you’re right about the way I approached the matter, it stinks. I came down on Windows 7 pretty hard when there could have been more serious problems to contend with. However, all my points can be backed up by example as well as proven workarounds to resolve these inconvenient truths. I have nothing to gain by stating these remarks as I am in the same business as you.
Another point I was trying to make is, not always is the latest greatest thing from a software company the best thing since sliced bread just because it’s a new version. (I also believe XP Pro 64 Bit was the first successful 64 bit OS). The reason why I've written what I have written is in hopes that some Microsoft programmer reading this form can perhaps bring up some of these points during their next meeting and take into consideration these changes for future builds.
For me, I'm just tired of having to go back to the drawing board each time they release a new product which is generally plagued by existing problems carried over and compounded by new and improved problems just because they decided to release a new version.
Obviously I hit a nerve in the community and maybe something will become of it. What drives me nuts are the people that know these little problems exist and refuse to admit that there are problems and turn a blind eye to them as if Microsoft never makes a mistake in their software. It’s no wonder so many people are targeting Microsoft software because its people like you who fuel them to rip it apart just to prove a point.
Very much like all those people who initially supported Vista out of the gate when Vista was released. I never pushed Vista onto anyone except for those that demanded I sell it to them. Then I gave them what they asked for, but I strongly advised them against the purchase as I told them to wait for Windows 7 and to stick with XP Home / Pro SP3.
I'm just looking out for public’s better interest who lookup to people in the industry who have already experienced the products and provide them with an unbiased stand point. A non salesmen version of what features are not mentioned in the sale of the software.
Slgried - I'm happy to hear the creativelement powertools software helped you. I guess to make a long story short everyone in this industry is plague with their fair share of problems and at the end of the day the last thing they want to read is someone focusing more on the negative then the positive. As the positives of Windows 7 completely out weight the negatives. If I offended anyone in my posts I'm sorry as it was not my intention. I'll only post useful information instead of flaming my frustrations on the forms. Thanks for bringing this to my attention.
Slgrieb - When did I give you the impression I was attributing bugs in third party software? All my complaints on this form topic have been personally experienced issues with a vanilla install of Windows 7 no additional software required. Just wanted to make that clear. The VPN issue I believe cleared itself up after I rebooted the Windows 7 PC and it hasn't surfaced since. I just reloaded Windows 7 for the third time on this PC due to hardware changes. Now that I'm starting from scratch again we'll see if the same problems surface again. Perhaps if you don't believe my words I'll take screen captures of all the problems and post links to them on this form. Just so you know i'm not making it up. But for some reason I still think you'll deny their existence.
Glad you got that off your hands
Hi Matridom,
I’m not sure I should bother to reply to this one. But I do appreciate your valiant effort to support your theories. However, I think you’ve mis-understood what I was trying to say.
I didn’t say XP Pro 64 bit was a commercial success. However at this point I wouldn’t be surprised if the form moderators started editing my posts for me. What I said and meant was it was the first legitimate attempt at 64 bit windows. (As indicated previously)
The Google reference was used just to make a point that I’m not the only person in the world with these type of error messages. Since you seem to think I’m making up these problems that don’t exist.
I also think you might want to look up the differences between XP NTFS 5.1 & 5.2 and Windows Vista / 7 NTFS 6.0. They are not identical versions between the two operating systems. (XP & 7)
Microsoft has done a great job in Windows 7 identifying faulty software without compromising the stability of the operating system. It is much easier now to tell when third party crap software is at fault.
I disagree with your statement about programs running with administrator privileges. No software should have admin control over the Operating system. If it needs to make changes to system files it should cache a copy of that file in memory and run it from memory. No program should be able to make any changes to the operating system. The operating system should merely be read-only after the installation and run much like a console operating system. Any changes required should be done through memory or temporary storage mediums and not the partition with the installed operating system. The only changes made to the operating system should be done through a hardened Microsoft systems account for the purpose of Microsoft updates only. This is where Microsoft has gone wrong with their operating systems giving programs too much control of the system. One day they will learn.
What I have learnt by posting on this form is that you are quick to blindly defend Microsoft while showing your true colors. Calling me down for speaking up about legitimate issues only showing your arrogance and your lack of respect for people who question. Just because I’ve posted a dozen problems that you can’t find answers to on the Microsoft Knowledge base or in your little pocket book doesn’t mean you should belittle me and call me a blatant liar. This form sure went downhill fast.
What's really neat is I've managed to capture a history of our conversations for all to read and let's just say it doesn't do you any justice. I am sure now it's just a matter of time before some fed up form administrator terminates this thread as its going no where fast.
1 Attachment(s)
The proof is in the pudding.
You know what, I'm more then willing to eat my own pie. Prove to me that NTFS will loose permissions. Prove it properly and i'll offer a complete apology and will be more than willing to admit that i was wrong. Create a scenerio where the problem can be recreated by others following a clear set of instructions. Then i will believe that NTFS has issue. Obviously you are confusing window versions with NTFS versions as these are not the same, but i'll overlook that.
( hint: try running the command: fsutil fsinfo ntfsinfo c: from your window 7 command prompt - you will need admin rights to run this, if you don't have a windows 7 system handy, I included a screen shot)
No one is going to buy your "known" problems until the proof is in the pudding, so i'm now calling you out. Prove it.