So when selecting output device, it was bugging me how much I had listed… time to clean it up… here’s how.
Over the weekend I was sorting out a few files and found a few “WLMP”, Windows Live Movie Maker Files. I opened one using VS Code and it very nicely listed all of the “assets” used in the project.
So I could rebuild the video using another application or download Movie Maker, now I knew Microsoft killed Movie Maker back in January, but I hoped I would find a download. I did not, which was amazing to me that Microsoft had managed to get it off the web.
I did find one site, so I downloaded it, then sent the file up to virus total and it came back clean. Great, so I installed it and when I opened it, I was presented with the following dialog.
Odd. So I played around with it and of cause it wouldn’t allow me to publish to YouTube or export to the project to a MP4 without buying it. So I decided to take a look at the icon properties.
Now looking at the properties and I noticed the exe is called “WinMovieMaker.exe”, so I took a little look in the folder and found the following.
If I run “MovieMaker.exe” it works no problem!
How is this site allowed to get away with this, I feel sorry for all the people who must be paying to “unlock” this. This is a valid reason why Microsoft should allow Movie Maker to be opened sourced like Live Writer was.
So I decided to install Visual Studio 2017. I have a 128GB SSD that I purchase a few years back now, I know I’m due an upgrade. 🙂
I wanted to play around with the Xamarin bit’s. So I selected what I wanted and it came to 40GB’ish, no problem I have a 1TB mechanical HDD.. so I changed the install location to D:\ drive.
As you can see from the screenshot above, I have selected D: drive and you can see the Android SDK bits selected to be installed top right.
So I click install and it fails with out of disk space error. What the installer doesn’t make you aware off is the Android SDK bits are installed to the C: drive!
As you can see the SDK grabbed 10Gb of the C: drive.
So there you go, make sure you have disk space available on your C: drive.
The most frustrating thing is a little warning would save a lot of wasted time.
I have logged this on user voice after tweeting Visual Studio.
You can go up vote it here.
https://visualstudio.uservoice.com/forums/121579?utm_source=t.co&utm_medium=referral
Happy coding and have fun! 🙂
I spent some time with this one.. As you can’t use the Report Viewer as you can with Web Forms, I have been using the URL Access to grab the form pass parameters and download.
The problem with this approach is that there is no way to change the name of the file that is downloaded.
This is the solution that I’ve come up with.
|
1 2 3 4 5 6 7 8 9 10 11 |
public ActionResult GetPDFReport(int? id) { string filename = "Generate Filename Here" NetworkCredential nwc = new NetworkCredential("username", "password"); WebClient client = new WebClient(); client.Credentials = nwc; string reportURL = "http://servername//ReportServer?PO&rs:Format=PDF&rs:ClearSession=true&Param1=" + id; return File(client.DownloadData(reportURL), "application/pdf", filename); } |
Have fun! 🙂
If you keep receiving the “replica is inconsistent” error message, check the following:
- Windows Backup Installed.
- Windows Update has been run to ensure the agent is the latest version.
If those have been checked, then you may have run into a known issue. WinRE, the Windows Recovery Environment partition is getting in the way, you can disable it by disabling WinRE on the server you wish to protect by running the following command:
|
1 |
reagentc /disable |
Now check replication again and it should now return OK.
Ensure you reenable WinRE with the following command:
|
1 |
reagentc /enable |
I received this error after browsing to \\server\printershare, right clicking and selecting connect, it proceeded as normal then the error was thrown, removing KB3170455 will resolve the issue.
You can check if it’s installed by opening PowerShell and run:-
|
1 |
get-hotfix KB3170455 |
this will return a list it if it’s installed. You can remove from the command line (doesn’t appear to be a PowerShell cmdlet at this time) by running: –
|
1 |
wusa.exe /uninstall /kb:3114409 /norestart /quiet |
KB3170455 seems to be the causing this issue and removing it will resolve the issue. I’ve not figured a how to install the printer without removing this update. If you have one then please post it in the comments.
This issue can be annoying, it requires the registry to fix, all the normal rules apply when editing the registry.
- Run regedit.exe
- Navigate to HKEY_CLASSES_ROOT -> jpegfile -> CLSID
- Right-click on “Default” (the Value Name) and select “Modify”
- Change “Value data” from {25336920-03F9-11cf-8FD0-00AA00686F13} to {FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}
When connecting to a recently installed Small Business Server 2011 using the Remote Web Access, the following error:
“This computer can’t verify the identity of the RD Gateway “remote.example.com”. It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance.”
would appear when trying to connect to a remote server or computer.
Note: These steps are best performed with Internet Explorer, as it involves downloading ActiveX controls.
- From a remote computer, go to your server’s website. This will usually be “http://remote.example.com”.
You will see a message saying “There is a problem with this website’s security certificate.” Click “Continue to this website (not recommended).” - Login to Remote Web Access.
- You will see several options – click on Public in the Shared Folders group.
- Open the Downloads folder, then click on Install Certificate Package.zip to download it.
- Close all open Internet Explorer windows.
- On your computer, extract the downloaded zip file.
- Run InstallCertificate.exe. When asked, choose to Install the certificate on my computer.
- You will see the message “The certificate is installed. You can connect your computer to Remote Web Access now.”
At this point a certificate called server–DOMAIN-CA has been installed in the Trusted Root Certification Authorities for the current user and for the local machine. - Open Internet Explorer, and go back to your Remote Web Access site.
- Attempt to connect to the server or other computer. You should see the following warning:
Tick the Don’t ask me again box, and click Yes to continue.
You should now open up a Remote Desktop Connection to the chosen server / computer.
NB: This is not my work, I wanted to post here for reference as it seems to work, original post : http://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-7-update-solution/f39a65fa-9d10-42e7-9bc0-7f5096b36d0c?auth=1
Windows Update has become quite problematic for Windows 7 users. For the past year or so, we’ve been working to find a solution that will work for you. We have found one that works very well indeed for most. We know for certain this works well for September 2nd Tuesday, known as Patch Tuesday. Which is today, and onwards till October 7th.
You want to ensure you get all your Windows Updating done before the next Patch Tuesday, October, 8. From that point onwards, there will be a very significant change in the way Windows Update works. Some may like it a lot. Some may dislike it intensely.
We emphasize that for this to work, you must follow exactly as this describes.
There are two main types of Windows 7 installations: 32 bit or 64 bit. You need to know what is installed in your computer. Click the Start globe, type system in the box. Choose System information in the list. The techie shorthand for 32 bit is x86 and for 64 bit is x64
1. Start Windows Update and change the Setting to Never check for updates. Close the Windows Update window. Some members recommend you return the setting to what ever you used before this operation, after you complete Windows Update. IF you do leave the setting at NEVER, Windows Update will no longer be automatic. From this point onwards, you are responsible for starting and installing updates. We recommend you do that a few days following the 2nd Tuesday each month.
2. Restart your computer.
3. The process starts by ensuring that there is nothing running that will prevent the update from working properly. Click on the Start globe and type services into the text box. Click on Services in the list that pops up. In the window that then pops up (its alphabetic), find Windows Update. Right-click on it (left-click if your mouse is set for left-handers) and choose Stop.
4. You are now going to download and install either one or two updates manually. In most cases only the first (KB3172605) of these is needed. If that produces a result that says the update is not appropriate for you computer, you need to first install the 2nd of these (KB3020369), then install the first (KB3172605). Choose the one that is for your machine — 32 bit (X86) or 64 bit (X64).
KB3172605:
32 bit
https://download.microsoft.com/download/C/D/5/CD5DE7B2-E857-4BD4-AA9C-6B30C3E1735A/Windows6.1-KB3172605-x86.msu
64 bit
https://download.microsoft.com/download/5/6/0/560504D4-F91A-4DEB-867F-C713F7821374/Windows6.1-KB3172605-x64.msu
KB3020369:
32 bit
https://download.microsoft.com/download/C/0/8/C0823F43-BFE9-4147-9B0A-35769CBBE6B0/Windows6.1-KB3020369-x86.msu
64 bit
https://download.microsoft.com/download/5/D/0/5D0821EB-A92D-4CA2-9020-EC41D56B074F/Windows6.1-KB3020369-x64.msu
5. After restarting your computer, wait about 10 minutes until Windows Update completes its tasks. Do not use the computer for any other purpose during this wait period.
6. Start Windows Update. It will take only a few minutes (unless, of course it has been many months since the last update) to come up with a list and download the updates you select. The process is quite normal as it always was from this point onward.
If your computer has not been updated for a long time, it may take longer.
#5.2.1 smtp; 521 5.2.1 : AOL will not accept delivery of this message
So after checking all of the obvious such as if any of the outbound servers were on any RBL, they weren’t. Email wouldn’t send but would send from a different server, then I removed the signature and the email sent!
I can only assume this was down to links to the images in the signature that AOL took expectation to. 🙂