Main Forum > Tweaking.com Support & Help

Broken apps issue

<< < (2/3) > >>

Shane:
It sounds more like the tech you talked with wasnt aware of the new powershell bug I found oon the newest build and so the auto answer when they cant figure it out is to either tell you to reinstall or place the blame else where.

Keep in mind many of the techs there are just people working to pay their bills, reading out of a book for the answers and can only go so far. The techs who know more and can do more get moved higher up and so on. So unless you somehow got to the holy grail of tech support they wont do much. A lot of them are good techs, hard workers, others, well not so much, we are all humans after all :-)

But I really think this bug needs to be made more aware. Far as I know I am one of the first who found it because the command was used in my repair program, so thats why i am not sure they know about it yet, they are running the commands themselves and see the problem but dont realize it is the command doing it. I post proof and how to repeat it, but I dont know any one at MS who would listen to me lol

Shane

kevlar_heart:

--- Quote from: Shane on December 01, 2015, 08:38:57 pm ---It sounds more like the tech you talked with wasnt aware of the new powershell bug I found oon the newest build and so the auto answer when they cant figure it out is to either tell you to reinstall or place the blame else where.

Keep in mind many of the techs there are just people working to pay their bills, reading out of a book for the answers and can only go so far. The techs who know more and can do more get moved higher up and so on. So unless you somehow got to the holy grail of tech support they wont do much. A lot of them are good techs, hard workers, others, well not so much, we are all humans after all :-)

But I really think this bug needs to be made more aware. Far as I know I am one of the first who found it because the command was used in my repair program, so thats why i am not sure they know about it yet, they are running the commands themselves and see the problem but dont realize it is the command doing it. I post proof and how to repeat it, but I dont know any one at MS who would listen to me lol

Shane

--- End quote ---

Hi Shane: Thanks for the shout out. I definitely understand the limitations of the initial level of Tech Support. They try hard, but aren't really given a lot of leeway in what they can do. I made it to the next level of support and we worked pretty hard at trying to get the Win 10 App Store and Metro Apps working. In fact, it was that upper level Support person who installed Tweaking.com WR  (what a great program!) He read your notes going from 3.6.4 to 3.6.5 and we recreated the errors....so SOMEONE in MS has seen the Store/Apps issue and the steps used to correct the issue and the inability of the powershell scripts to successfully repair the problem. I've trolled several Forums with the results and everyone (so far) has no other solution other than the Powershell scripts created to repair the Store/Apps back in August/Sept 2015.

The "not certified" cop out is reasonable except that MS pushed the Win 10 upgrade to any computer that passed the initial compatibility test. As far as I know, there were no cautions about proceeding with the upgrade ONLY if the computer mfr was supplying complete Win 10 compatibility. A simple LUT would tell the installer whether the computer was on the list, not on the list, or specifically excluded from Win 10 support. It's not as if MS wasn't snagging data when they pre-positioned 3 GB of installation files.

Anyway, thanks for your continued hard work for us all. My wounded warrior will run the applications I need for work. I am just missing the complete Win 10 experience.

Shane:
That is awesome that you got someone to read my notes and got them to confirm the bug, now lets hope someone there listens to him lol

As of the latest updates as of today the bug is still there.

Shane

kevlar_heart:
Hi Shane, I was going to PM you, but figured you don't accept them for peace of mind issues ...

I hope this finds you well -- try looking up Coffee Labs Roasters in Tarrytown, NY...great coffee. I'll send you some if you like.

With regard to the Powershell fixes for App Store registration and Metro Apps installation, I am running into a roadblock wirh Microsoft Answers tech support. To wit - MS is defaulting to its position that if the host computer was not certified for Windows 10 by the manufacturer, any artifact in the Win 10 installation is the product of incompatibility rather than a bug in Win 10. Despite my protestations that Win 10 worked like a champ before the Threshold 2 update, MS is not recognizing the App Store/Metro Apps as a "known issue." I have a Dell Latitude and its signed drivers are damn near identical to another model that was certified by Dell. I have ZERO other compatibility issues running rendering software and certain image processing testing applications...so who's zooming who here?

I've poked around the Registry Keys for the Apps and got hopelessly lost comparing working vs. non-working apps. The Store itself is there but somehow not reachable...

Anyway, that's my update. If I get some actual NAMES from the Windows Answers crew (one of them installed Tweaking.com to fix the issue), I'll try to persuade him or her to review the notes I've compiled and reach out to you if that's OK.

Be well. Rock on...get some sleep!  :wink:

Julian:
windows 10 (1511) 10.0.10586 Tested to still have this issue.

Navigation

[0] Message Index

[#] Next page

[*] Previous page