Quantcast
Channel: General Office Development forum
Viewing all articles
Browse latest Browse all 2257

MS Office 2016 TP messed 2 laptops

$
0
0

After trying to test drive Office 2016 on 2 of my laptops it didn't want to run (encountering unspecified error!-which is quite annoying by itself) when I uninstalled it, my previous version of office 2013 crashed. I managed to do a System Restore, but on one of the laptops OneDrive for Business is not running now - it only says "Something went wrong" (again very informative :-( ). Uninstaller entry in Remove Programs of OneDrive for Business is returning error message!? WTF?

I am really confused with Microsoft lately. I have the feeling that everything you launch for testing is not working by default. What is the point of launching it then at all? I think there is something messed up with your QA process. I am aware that these are technical previews, but in the past they worked on majority of the machines and there only few bugs to be ironed here and there - now it is vice versa - bricking machine is what you usually get. Now how  should I deal with it?

I have more or less the same experience with Windows 10 TP (just to mention). 

And when you need to comment on something or find help - it so complicated - you need to have a PhD in order to find the thousand of websites and domains operated by Microsoft with hidden forums, registrations, sub-forums and so on - I have the feeling you want to make me give up intentionally. Why are you specializing in making things more and more complicated? I really can't understand where this company is headed towards?

I am giving up on testing any of MS's products from now on...

I continue to search for reasonable solution of fixing my PC without forcing me to re-install Windows (I tried uninstalling and re-installing the whole Office 2013 package, but it didn't work so far).

 

Regards, 

Biser Borisov


Viewing all articles
Browse latest Browse all 2257

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>