Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - whiggs

Pages: [1] 2 3 4
1
Tweaking.com Support & Help / Support for windows 11
« on: October 05, 2021, 08:54:15 PM »
Hello.  You are probably already aware of this, but Windows 11 (https://www.microsoft.com/en-us/software-download/windows11) was officially released today.  I Just wanted to make sure that you are aware of this so that you can begin working on updating tweaking AIO Repair so that it is compatable with windows 11, as it does not appear to be at the moment.

2
Tweaking.com Support & Help / Reparse point scan and repair error
« on: May 03, 2020, 02:29:20 PM »
Hello.  So I was running a reparse point scan and repair on one of my computers, and I noticed that, despite the reparse point being valid  and working, the scan is detecting an invalid symlink during the scan and failing to repair the problem during the repair.  This is the invalid item that the scan finds:



Below is the info in the log file when trying to repair the above item:

Quote
+-------------------------------+
¦[STARTED] [5/3/2020 5:03:00 PM]¦
+-------------------------------+
Running Repair on C:\Program Files (x86)\Google\Chrome Remote Desktop\CurrentVersion

   
  • Command to Run: Create Target Path/Folder .\83.0.4103.2\
  • Calling SHCreateDirectoryExW
  • SHCreateDirectoryExW Returned An Error, Error: 161 - The specified path is invalid.


+--------------------------------+
¦[FINISHED] [5/3/2020 5:03:00 PM]¦
+--------------------------------+

3
Tweaking.com Support & Help / Re: 1909 version ETA?
« on: November 14, 2019, 06:47:24 PM »
Futhermore, the fact of the matter is, based on how the application seems to work, the repairs that it performs are dependent on the operating system installed.  That being the case, the application needs to be updated with the fixes for 1909.  If the same fixes from 1903 are applicable, then we need to know that, so we can then create the necessary file with the content copied from the 1903 file.

4
Tweaking.com Support & Help / Re: Win 10 Ver 1909
« on: November 14, 2019, 06:43:45 PM »
Same here.  After I did an in place upgrade to windows version 1909. 

5
I just ran the read-only chkdsk scan in Windows AIO repair on one of my machines, and good thing I was paying attention since, despite the fact that I saw the console text display an error in the file system, Windows AIO repair reported in the main application window that no error were found when the process completed.  Attached is the log file which the chkdsk scan generated when Windows AIO repair reported that there was "no error"

6
Tweaking.com Support & Help / Re: issue with reparse point scanning
« on: December 28, 2017, 06:08:55 AM »
Seems the issue is not limited to just the reparse point scanning either.  I looked and verified that their isn't an entry in the PSModulepath environment variable that has the path indicated in the below scan result:
Checking Environment Variables.
│ Started at (12/28/2017 7:18:10 AM)

│ This folder in the 'PSModulePath' variable doesn't exist: C:\Progr

│ Problems were found with the Environment Variables.
│ You can use the Repair Environment Variables Tool at the bottom of this Window to try and fix these problems.

│ Done Checking Environment Variables. (12/28/2017 7:18:10 AM)

7
Tweaking.com Support & Help / issue with reparse point scanning
« on: December 28, 2017, 04:28:21 AM »
So I just performed a repair install of the latest version of Windows 10, and first thing I did when the repair was complete was boot into safe mode and run the pre-scan.  One thing I have noticed is that, whenever I perform a repair install and then run windows AIO repair (to verify that the os doesn't have any issues), the reparse point scan always finds the same errors each time I perform a repair install: reparse points associated with my Office 365 Office suite installation are always "erroneous", as well as reparse points associated with my Graphics card driver/software:
canning Reparse Points.
│ Started at (12/28/2017 7:03:48 AM)

Reparse Point: (Type: JUNCTION) (Name: NvTelemetry) (Original Path: C:\Program Files (x86)\NVIDIA Corporation\NvTelemetry\plugins\NvTelemetry) (Target Path: C:\\C:\Program Files (x86)\NVIDIA Corporation\NvTelemetry\plugin) (Creation Time: 12/23/2017 7:25:45 PM)
Target Path doesn't exist!

│ Problems were found with the Reparse Points.
│ You can use the Repair Reparse Points Tool at the bottom of this Window to try and fix these problems.


It is also important to note that the original path is very much valid (verified using nirsoft tool "NTFS links view"), so something isn't quite working with the reparse point scan.

8
Tweaking.com Support & Help / Respectfully disagree
« on: December 23, 2017, 06:24:45 AM »
In the Windows AIO application, I believe that the "scan and repair reparse point" functionality should be a valid fix in of itself, or at least its importance in resolving issues shouldn't be undersold.  Example: I recently created a custom install.wim of the latest version of Windows 10 for use in deployments, but when I deployed the image, the system was slow and my applications kept crashing.  Turns out that, for some reason, when I created the custom image capture (which, for those who don't know, usually entails booting a fresh install into Audit mode, which uses the administrator account to allow you to make changes which will be captured to your OS), all of the built in administrator's default reparse points had been deleted.  Using Windows AIO repair to add them back in resolved the issue instantly.  Still need to rebuild the image, but my point being that employees at the company I work for also use Windows AIO repair, and they just skip to the repairs without even looking at the other features.  I have tried to dissuade them from doing this, and actually follow the recommendations outlined in the help file, but there are a few who don't care.  Anyway, I would highly recommend that the scan and repair reparse points fix have its own repair entry, or at least not be downplayed by putting the text "THIS IS NOT A FIX" right at the top of the page where the repair is located.  Just my 2 cents..

9
It was in windows 10 anniversery update Enterprise edition (so not the most current release, the previous release from the current release).  Haven't tried it on any other system.  Also, didn't run the command until after I found the issue.  Also, in regards to your statement that registering all of the dlls in the system32 folder is a bad idea, try doing a google search of the error this post references and see how many microsoft forum sites recommend doing just that
https://social.technet.microsoft.com/Forums/ie/en-US/dd05eca6-0f10-4b43-a860-6846cea310e7/error-an-attempt-was-made-to-reference-a-token-that-does-not-exist?forum=winserverManagement
https://social.technet.microsoft.com/wiki/contents/articles/6338.microsoft-management-console-an-attempt-was-made-to-reference-a-token-that-does-not-exist.aspx
I could go on and on, but I think the point has been made

10
There is a bug with Windows AIO repair.  After I run the repair "register system files", if I have the Remote Server Administration Toolkit (RSAT) is installed on my machine and I try to open "Active Directory Users and Computers", I get the above error and the one attached to this post.  I already found the fix: I simply have to re-register all of the dlls in the "System32" folder with the below command, and it starts working again immediately:
for /f %s in ('dir /b *.dll') do regsvr32 /s %s, C:\Windows\system32
EDIT:   Usually this resolves the issue.  However, and I don't know if Windows AIO repair causes this issue or not, but the above command did not fix it for me this time.  It took me a lot of research to find this, but the reason that the error is occurring is because certain registry keys were improperly modified:
HKEY_CLASSES_ROOT\mscfile\shell

When I expanded Author\command, open\command, and RunAs\Command, the default registry key for each entry was pointing to the 32-bit version of the mmc executable in '%SystemRoot%\SysWow64\mmc.exe "%1" %*'.  These registry keys need to be changed to point to the mmc executable in the "system32" folder instead.  Then it worked like a charm.


11
General Computer Support / Re: On screen Keyboard keeps crashing
« on: June 23, 2017, 10:02:59 AM »
Windows server does not support creating system restore points.  I have actually tried replacing the file, but it will not let me because the "DHCP service" is supposedly locking the file

12
General Computer Support / On screen Keyboard keeps crashing
« on: June 23, 2017, 07:30:17 AM »
Hello Everyone,
So I had a quick question involving an the fact that my on-screen keyboard will crash after I close it and only after the first launch since reboot on my Windows server 2012 R2 machine.  In order to troubleshoot, I mounted the wim from the base install media and compared the osk.exe files (the on-screen keyboard executable located in C:\windows\system32), and found that the hash values for these files was different.  The date that they were modified is also different.  So here is my question: Windows server 2012 R2 has been in use for quite some time, so is there a possibility that some Windows update or Windows feature that I have installed modified the on-screen keyboard executable so that it is no longer the same file that is included in the base installation media?  Also, if anyone has any idea as to why the on-screen keyboard keeps crashing, please let me know.  While it is not preventing the server from functioning correctly, it is an area of concern.  BTW, all running the following shows no problems with the os:
sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk C:

13
So I found an issue.  When launched, the metro apps' windows do not resize properly.  for example, if I were to increase the size of a metro app window horizontally on the right side, the scroll bar which would allow me to navigate down the page would stay right where it is and would end up in the middle of the expanded window.  SO I did a registry restore and simply ran the PowerShell command which I know will resolve most store issues (Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}), and not only did the icon change back to what it was originally, but the store apps seem to work again.

14
So tonight is the second time I have run the Repair metro apps repair on a device (as in two separate installs, two separate incidents) running Windows 10 creators update pro x64.  And this is the second time that, after the repair was completed and the device rebooted, the Windows store icon has changed from the default:


To this:


While the Windows store apps APPEAR to be running normally (meaning that the problem that I was having which prompted me to use the repair in the first place was resolved), I have no doubt that something will crop up, because (call me a cynic) something always does..... :sad: :sad:

15
This is only applicable if you have the creators update version of Windows 10.  Version 1703 Build 15063.250

16
Hey everybody.  So I wanted to report that, since Microsoft has decided to ignore the issues prevalent in the creators update of Windows 10, I did more digging into the issue.  I then found a blog post which confirmed that the corrupt Windows package file is indeed the cause of DISM not working correctly, and it does come that way right out of the box.  However, the blog post also offers a solution: Just delete the references to the corrupt package file from the Windows registry.  There are a total of 4 registry keys: 2 are located in both
 "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex" and
 "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages".  You will want to delete the two registry keys which contain the name of the corrupt package file: "Microsoft-Windows-TestRoot-and-FlightSigning-Package".  You will have to edit the key permissions in order to do this, as you do not have the permissions by default.  Once you delete those keys, then navigate to "C:\Windows\servicing\packages" and either move or delete the 4 files which also contain (and begin with) "Microsoft-Windows-TestRoot-and-FlightSigning-Package".  Then, run the scan again and it will continue to completion (at least as long as nothing else is wrong).  blog post can be found here:
http://borncity.com/win/2017/04/26/windows-10-v1703-fix-for-dism-error-0x800f081f/#comment-1215

17
So this was my bad.  After running the fix IE repair, edge for some reason no longer works.  my bad

18
Another issue that has been pointed out before is the issue with the corrupt digital signature detected during the pre-scan for 1703.  Also, I might as well report (since I have experienced it multiple times now) that the "repair IE" fix actually doesn't break IE, it breaks edge somehow.  After running the fix in version 1703, when you try to launch edge (no matter what manner of edge or app store reset I attempted, other than restore the registry), it just hangs on a white screen until it auto closes.

19
I just mentioned that the computer is domain joined.  The user account itself is being created locally, which has worked in the past.

20
I will be sure to keep that in mind.

21
I have tried to create a local user on a domain joined computer using the technician toolkit 3 times, and each time it reports error code 0, but no user is created when I click refresh.  FYI

22
Uncanny!!!  I would make that mistake as well.  Not to argue the finer details, but I fail to see, even if I were the one who posted that post, how that would be considered inconsiderate.  The likeliness of getting an issue resolved increases when the number of eyes that see it increases, until that one person who knows the answer finally replies.  So if anything, I would think that limiting the issue to just one web sites forum would do yourself a disservice, as it severely limits the number of people who can see and reply to your problem.... 

23
I actually noticed this while I was trying to write a script which creates an internet explorer window, I kept getting the error:
> IE.au3 T3.0-2 Error from function _IECreate,  (Browser Object Creation Failed)
So, I went to check out internet explorer and noticed that the application is missing entirely from the start menu.  In fact, the only way to find it is by searching with Cortana.  I think that Internet explorer was updated in the creators edition (see pic), and applying the Windows AIO repair for IE to the Creators update version has dis-associated it from the operating system.  For example, I tried resetting the internet settings from Internet options in control panel.  Now normally, if there are any IE processes running, trying to reset internet settings will generate a popup box telling you to close IE first.  Even though I had Internet Explorer open (after I found it with cortana), I was still able to perform the internet reset.  When I launch it, it appears to function correctly, but I am very troubled that I am unable to script with it anymore.  Any thoughts?

24
thanks for the verification.  BTW, I did not post this issue in bleeping.com's forums.  I don't really use that site.  What made you think I did?

25
Thank you for your feedback.  So SFC does not report any corruptions.  In fact, if you look at the log file I posted in the original post, it states that "The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually."  And since there is only one file, I assume that it is referring to that file.  My concern is that I have encountered this issue on two different machines in the span of less than 24 hours.  It occurred immediately after I performed an in place upgrade, so, since I assumed something must have gone wrong during the update, I ripped the iso to a usb and did a clean install.  Booted it into audit mode, did some basic installs, ran it again and boom, it was happening again.  That kind of error should not be occuring on a brand new machine build, much less an in place update where it was working fine before, you know?  While nothing may is necessarily wrong right now, I would think it would be very important to get that command to work, as it is a major repair tool that many people and applications (including Windows AIO repair) use to fix systems.

Pages: [1] 2 3 4