• 914-788-9210

Twas The Night Before Windows 10 – A Christmas in July Story

by Patrick Rardin in Technology

Twas the night before the release of Windows 10, and not a creature was stirring not even an infrared mouse! So I crept to my computer quietly and carefully and I began my venture into an early test of Windows 10!

I didn’t really want to be the Grinch who stole Christmas (and that’s exactly the way I felt) when I sent out my emails, telling everyone not to upgrade to Windows 10. I also contacted many of you by phone alerting you to the dangers and risks of installing Windows 10, and again I felt like a Grinch, telling a child Christmas morning, not to open up his new present.

So here’s a recap of my little experiment. Let’s call this the Windows 10 experiment. I said to myself “what the heck I’ll just do the upgrade on my home PC, that way I won’t disrupt anything at work and if it’s successful, I can allow others to upgrade their own PCs!”, not depriving them of the joy of this new operating system.

I immediately jumped in and launched the upgrade process. The process was relatively quick and when I was finished, I was presented with a delightful new screen. The other new features of Windows 10 were beckoning me and indeed looked quite tantalizing.

However, I realized I had to get serious and start using it. The first thing I did was try to open Quicken and to my surprise I got an error message saying that the file was read only and that I would have to move it somewhere else in order to use Quicken. Well, I figured this must be some new security feature, so I moved the file and opened Quicken and everything seemed fine. Now to another program “Oh no!”, I exclaimed. This program wouldn’t open either and I was getting that same read only error message.

At this point, I decided to go online and do a little bit of research; to my surprise, I wasn’t the only one experiencing this problem. Many technical solutions popped up and not one of them could resolve the issue; so I found myself resorting to command line instructions (like in the days of DOS, not that I’m old enough to know anything about those days, LOL). The DOS commands resolved the problem about 80% of the time.

Sadly, my experiment was really starting to tarnish. I tried doing other things in Windows 10 and to my dismay, I could not. For example, I have my Quicken setup to download the latest transactions from the bank and when I went to the internet to do this, it kept telling me my password was no good! And, if I kept trying I would be locked out. So I researched this only to find out that the brand new Quicken 2015 that I had just installed would not work with Windows 10 and I would have to wait for the release of Quicken 2016.

OK! At this point, I was really frustrated and wanted to get back to using my home computer. Microsoft had stated that anyone who installed Windows 10 would have 30 days to undo the installation. Therefore, I followed all the instructions on reverting to Windows 7 (BTW – THE MOST AWESOME WINDOWS EVER!) and was presented with the following message “we’re sorry, you cannot revert back to Windows 7 because the files required to do so have been deleted”.

I love my customers dearly and I hope this little story explains to you exactly WHY I set out to alert you all! Unfortunately, I now have a brick for a computer. This is just one man’s story and the Internet is replete with more stories like mine. Ironically, most of the news seems to be touting the wonder of Windows 10 and I’m not sure if these are paid ads by Microsoft or just misinformed reporters.

It is quite possible that if you do not do an upgrade, but you do a fresh installation of Windows 10 or if you buy a computer that has Windows 10 already loaded the experience may be quite different. That will be my next experiment and I will keep you all posted!

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>