The outlook 365 in windows 10 behaving strangely. one day suddenly it stopped working and I no longer could synchronize my emails. (Probably due to an update).
When windows is connected to my mobile hotspot the outlook works fine but as soon as I connect back to a home wifi network it stops synchronizing emails. I suspect that it is problem with the wifi router but all other devices such as phones and tablets are connected to wifi and emails and other functions work fine. I tried with another email client (Thunderbird) but the problem persists.
Last night I had a three hours session with Microsoft support but all we could conclude was above.
OK, Finally, I found a solution. I did everything except uninstalling and reinstall office 365. I reinstall Office 365 and outlook works fine now.
Related
Good day
I have something weird happened to my Lenovo Legion 5 laptop (Windows 11), one of them is the error below.
enter image description here
And the other weird stuff is, some of the applications that cannot be opened like my Visual Studio 2022 community,SQL Server Express, Microsoft Edge, Google Chrome, Avira (yes I can't open the UI of my Avira), iTunes, MS Office and etc, while Spotify, Steam, Need for Speed Most Wanted are all working properly. I have to repair most of them, and for the Visual Studio, I have to run it as an administrator in able for this to run.
Here's a sample of the error
enter image description here
The last time I remembered before it all happened is I install the IIS with .NET Framework 3.5 and .4.8 with it, does this have an impact on what's happening on my laptop or there are other factors?
Thanks and regards
I have re-install all the apps,but for FnHotKeyUtility.exe, it is still recurring error on my laptop.
I would like to remote control a Windows 10 Mobile Phone from a PC. I only found the remote Desktop App which allows a Phone to remote control a PC.
Connecting via RDC to the IP address shown in "Phone, ..., For Developers, Device portal" does not work.
According to Windows Central there is a new feature Project to this PC in the Win10 Anniversary Update:
"
On Settings > System for the Anniversary Update there is a new Project to this PC settings page. This is a new feature in the new version of the operating system, which is essentially another way to remote access devices. The feature allows to project your Windows phone or computer to another Windows 10 PC with access to control their keyboard and mouse using the Connect app.
"
After a lot of digging (searching), I ran across a company called ISL Online. The link is here: ISL Online
For my scenario, I want to remote control the W10M device via the internet/network, similar to how you would using Remote Desktop Connection. This seems to be one of the few, if not the only companies out there that has a solution for this.
I am now using it and it works great.
I cant find information on this error anywhere. I am connecting to a brand new lumia icon (AKA lumia 929). Dev account is registered. I have attempted:
reinstalling windows phone SDK
restarting phone
restarting computer
ensured the app runs on the emulators properly. the only required capability of this app is network. Capabilities have not been changed from the defaults since the project was created. none of the manifest xml files have been touched.
ensured phone software version is up to date
ensured apphub account is valid and active
ensured the windows phone developer registration tool worked, unregistered and re-registered the phone to make sure
restarting the "ip over usb" windows service thingy
changing the platform built target to ARM or AnyCpu (no difference, same error)
tried alternate deployment methods such as windows phone power tools (the xap deploy) and I get the same error when trying to connect (so I know it's not an issue with visual studio, nor is it an issue with the app code)
I can successfully deploy separate code to a separate WP7 device (so I know it's not an issue with the computer)
tried multiple usb ports
tried two separate laptops
tried visual studio 2013 and 2012
The behavior is this:
Connect the phone via usb and unlock it
Attempt to connect to phone via windows phone power tools OR deploy an app via visual studio
System hangs for about 90 seconds and seems to time out
Error appears
I am able to view the phone contents, name it and explore it on my laptop, but when it comes time to deploy something I am stuck.
Error message is simply: 0x89371B01
What does that mean? Has anyone else run into this?
Have you checked the device drivers on your Windows 8.1 machine? It could be a driver issue with your USB drivers on the computer.
I have also found that, once you get it connected, going into the Device Manager and deleting the device from there and forcing it to reload has helped me in the past.
Out of curiosity, try running "sfc /scannow" at a command prompt on the PC. It may require admin elevation. I've seen some bizarre behaviors due to dll problems in sxs in win 8.1, wondering if this could be caused by that kind of thing.
Couple of things to try:
Have you installed the GDR3 Emulators and tried running it on the 1080p emulator? It looks like the 929 is a 1920x1080 phone and will have the latest the latest updates installed. First place to check.
Based on this feedback in another stackoverflow question it looks like someone was having a similar issue and disabling Hyper-V resolved it for him. If you disable Hyper-V and it works, try re-enabling it and see if you still have the issue.
jmshapland had the correct answer for me, with the same issue. Disabling Hyper-V did the trick! No thanks to microsoft phone dev center forum posting on the issue..
http://social.msdn.microsoft.com/Forums/wpapps/en-US/24bd3e48-e7b4-4d00-8d69-193f49989ce0/0x89731b01-error-during-deploy-to-device?forum=wpdevelop
Looks like I'll be disabling Hyper-V to test on my device, and re-enabling to work in emulator mode:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
OK I was able to come up with a repeatable solution for the issue. Im HOPING that by posting this I dont tempt fate and have the phone not work again!
Here are the steps I did to resolve it (not sure if all of them are necessary):
On phone, disable wireless
Connect phone to laptop
Open device manager and click to show ALL HIDDEN DEVICES (including hidden devices is important)
Uninstall ALL phone-related devices (one in portable devices, several in USB
devices) anything that mentions lumia must go
Disconnect/reboot phone
Reboot laptop (there seems to be a process keeping the port open)
I had connectivity, then I lost it, then I re-gained it using these steps and it seems to be reliable for me (so far)
I just reinstalled my laptop on Windows 8 and VS2012 but now i can't connect to a private TFS server but it work well on my desktop with Windows 7 and VS2010.
For a lot of people this problem was solved by clearing IE cookies, but it don't work for me.
I would contact the TFS administrator and check how authentication is configured on the server.
Also, be sure to use your full domain name(e.g DOMAIN_NAME\USER_NAME).
I don't believe this has anything to do with the browser implementation you decide to use.
I have a Excel work sheet with a lot of hyperlinks (both to external documents and to other tabs on the same document). We recently moved over to a DAV server to have our files easily available from whatever location we are on. The problem is that some of our machines are unable to use the hyperlinks in the existing documents (nor can I create new hyperlinks that work in existing documents).
We have tested this with Windows Vista and Windows 7, both running Office Professional 2007 and neither can get the hyperlinks to work. We have tried on a Windows 7 machine with Office 2010, and this works fine, as well as a recently set up computer with Vista and Office 2007. It only appears to happen on our existing machines.
What we have tried so far;
Disabled Firewalls
Disabled Antivirus
Reconnected using different DAV users
The Windows7 With Office 2010 runs the same Antivirus and Firewall as the other two machines, but they have not been disabled on this machine and it still functions as intended.
Any recommendations on what might be causing this are more then welcome.
The problem causing this was that the WebDrive program we use to prevent having to authenticate repeatedly used the Username of the machine as part of the virtual server address, this caused issues as our users have both first and last name accounts generating a space in the server name (which is not valid).